Database view not visible to users for reporting

[toddpreece]

The other day I created a database view that combined fields from incident and sys_journal_field. I created a report from this and itil users are able to see and use it with no issues.

Yesterday I created a largely duplicate database view that combined fields from task and sys_journal_field. The only differences between the two views are the tables involved (task vs. incident).

However, itil users are unable to see the new view as a table to create reports from, nor are they able to see the report I created w/o getting "Security constraints prevent access to requested page". I've looked at the ACLs on the two views and all seems identical.

[Michael Fry1]

Since one of the tables is a sys table, did you try modifying the UI Properties and allow reporting on that table https://docs.servicenow.com/bundle/london-performance-analytics-and-reporting/page/use/reporting/con...

[Phuong Nguyen · Accepted solution]

HI toddpreece,

For the user to be able to read the DB view report you shared with them, they need to have read access to the tables involved in the database view. The user might have read access to the incident table but *not* the task table and that is why they see the error. They may or may not need to pass the "report_on" type ACL to be able to create report on the database view themselves. Please let me know how it goes.

Thanks,

Phuong

[Tanmay14]

Hi,

I have a similar sceanrio where database view is created on 3 tables viz. sn_hr_core_case, metric_instance and metric_definition and user has read access to recrods on these tables. When this user (non admin) pullls up dashboard, a multi pilot table report with count based on this database view shows up data just fine but when this user clicks on one of the count to go to the list view, it just opens the database view and says 'No records to display'. As admin I can see the records just fine.

Thanks

[toddpreece]

Phuong,

Thanks, you got me pointed in the right direction. I ended up adding a read-only ACL on the task table and it worked. Still not 100% sure why it was needed since it looked to be in place from other ACLs but I wont look a gift horse in the mouth.