Database view not visible to users for reporting

toddpreece · ‎03-26-2019

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.

Phuong Nguyen · ‎03-26-2019

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

View solution in original post

Phuong Nguyen · ‎04-01-2019

Hi Todd,

Glad I could help! It is tricky when it comes to ACL for sure!

Jha · ‎01-18-2022

Hello All,

Actually I have same issue related to the above topic.

I have created the query using the CMDB query Builder as below and run it successfully .

Its showing the record as per the below format but the issue when I asked the end user to validate the same they are saying version and Class fields are empty for them .