This question has arisen because I have many tasks where it would be very helpful if I enabled list-view editing for the Report [sys_report] table. By default, list-view editing is disabled on this table, though I have not been able to find any documentation on this restriction or why it was done.
QUESTION: What necessitated this list-view edit restriction on the Report [sys_report] table? As I'm sure there is a good reason, and I don't want to make more problems than I resolve by disabling this restriction.
As Adam Stout mentioned, the report table is loaded with dependent fields dependent on the report type, so building a report from the list could be quite complicated. Disabling it across-the-board would avoid the necessity of complex documentation/questions/answers on how to set/troubleshoot records users have modified via the list interface.
I get it that users could get lost/make a mess in the list view interface, but it is also capable as serving as a valuable config tool. I would think that a role-based list-view edit constraint could be beneficial for reports administration. That is, unless I'm overlooking something. That is precisely what I made this question to verify. And to figure out how to enable it, too, if appropriate.
Are there any other reasons that it is disabled?
Thank you for your time!
List-view edit example
As brought up by
To Enable List-View Editing:
In the List Control menu for the Reports [sys_report] table, change the List edit type setting to Save immediately (cell edit mode). Save the settings.
To Role-Constrain List-View Editing:
Enable list-view editing (above) and then reproduce the following ACL to restrict list-view editing on the Report [sys_report] table to admins and report_admins only. (Thank you @Chuck Tomasi)
