Create queries for custom views, reports and queries#7650
Conversation
…ow handled in the update service for the CustomViewsTable.
labkey-adam
left a comment
There was a problem hiding this comment.
See questions about potential cross-container issues
labkey-adam
left a comment
There was a problem hiding this comment.
Manual testing verifies those cross-container issues are present. For example, apply a folder filter and attempt to delete a report that's outside the request folder.
Give it another try, I think I've addressed all of those cross folder issues. |
labkey-adam
left a comment
There was a problem hiding this comment.
I think container filters are allowing rows based on read permissions (the default) when it should be admin. I think you need to override getContainerFilterClause().
|
Good catch, done. |
|
One issue and one request:
|
Default sorts for reports, customViews, and queries tables.
Rationale
Tracking issue : https://github.com/LabKey/internal-issues/issues/1078
This PR introduces admin-only queries to replace (or create) standard LabKey table infos for : custom views, reports and queries. Details include:
queryschema that's available to admins only.query.CustomViewstable that exposes that table (shared and private views).query.Queirestable that exposes the querydef table.core.Reportstable that exposes the reports table, also restricted to admins.