Mistakenly saving report specs

Here is feedback/feature request. Basically - saving standard reports is a major win, but anyone who uses a saved report can also corrupt it by changing something and saving it. And Save is ambiguous in US english at least to the non technical.

Unfortunately, the utility is lost if the report might be wrong and you have to double check it every time. Here is my report and request, if you agree please also do so:

This issue arises where you have many people accessing the same pool of saved reports, so I didn’t see it in beta. I’m running into an issue where reports are getting corrupted because the employee mistakenly clicks Save instead of Export, and I have had corrupted reports. I will of course try to deal with it in training, but if there were simply a checkbox that had to be unchecked to save, that would probably deal with 90%+. (The user could still change a spec or date range and export/view, they just can’t save the report unless it is unchecked.)

1 Like