Since the update to UTAH users can't read or create some reports

[New Developer_S]

Hi Folks,

After Utah upgrade , some users are unable to create / read the reports though they have ITIL role . What is the solution for this ? Getting and error like ' Access to the content is denied based on report_view ACL´s.

I have checked the ACL on that particular Table which user raised the issue , the report_view ACL is set to admin user for Type sys_auto but not for that particular Table. .please find the screenshot

.

How to troubleshoot and fix this issue ? 

Kind Regards

TIA

[Daniel Borkowi1]

Hi @New Developer_S , this is caused by the new report_view acls. You need to ensure that there is a Report_View ACL for you users roles who should see the reports.

See this: https://docs.servicenow.com/en-US/bundle/vancouver-now-intelligence/page/use/reporting/concept/repor...

Greets
Daniel

Please mark reply as Helpful/Correct, if applicable. Thanks!

[New Developer_S]

The strange thing here is the particular user who is having the above issue has got all roles set to true  . Please find the attachement .

[New Developer_S · Accepted solution]

Hi , 

I am able to find the solution to this.

I have added a custom ACL of type 'report_view' and added a custom role to that ACL. Then added that custom role to user. This resolved the issue.

[Hristo2]

- After the upgrade it seems that the report_view ACLs can't be disabled and have to be updated
- Updated the ACLs for incidents, tasks, change requests and requested items (only read ACL's), so now the users are able to see the reports.
NOTE: you should update the ACL's for the tables that we are using (incidents, tasks, change requests and requested items). If you are using different tables you should update the ACL's for them too.