Even after configuring report_view ACL, user facing issue to view the report

[Dee S]

Hi,

There is a custom table let's say 'u_catalogitem'. This doesn't have any ACLs configured as of now and table is only accessible to admins.

There is a user (who is not admin) asked to create a report of the type list for the table 'u_catalogitem' as he cannot access table.

Even after the report is created he/she will not able to access report due to access issue.

I was suggested to configure 'report_view' acl (admin override is true) - row level (u_catalogitem - None) and add attribute condition as -> Group is 'any one of the user's group'.

Even after configuring the report_view acl. User is still getting an error "Security constraint prevents access to the page".

Is there any way that I can achieve this using report_view acl?

[Hemanth M1 · Accepted solution]

Hi @Dee S ,

You can't view list of records if don't have read access regardless of the report_view.

Why don't you create a scheduled report and send.

Scheduled Report reference: https://developer.servicenow.com/dev.do#!/learn/courses/washingtondc/app_store_learnv2_reportanalyti... 

Hope this helps!!!

[Dee S · Accepted solution]

Update on the question asked:

 As @Hemanth M1 mentioned here, You can't view list of records if don't have read access regardless of the report_view. Report_view ACL is basically to restrict report access.

So, read access should be given and then report_view acl should be created and given to the required roles