Database View fields not visible via a Report
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-05-2018 03:00 PM
I'm running Istanbul. I have a Database View combining the Incident and Problem tables. I have generated a Single Score report counting the number of Active problems. The report has been shared with Everyone. The report runs successfully and clicking on the Single Score should show a List of the Problem records, but it is resulting in a Number of rows removed from this list by Security constraints message.
I have an ACL set up on the Database View to allow ITIL users to Read (--none--) the Records and both the Incident and Problem tables are available to the ITIL users. Ironically, the same report works on our Development instance. As far as I can see, the Database View, Report and ACLs are the same...what am I missing?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-06-2018 05:27 PM
Ok Great. You dont need the ACL with Table.* . Only keep Table. None
Please mark this response as correct or helpful if it assisted you with your question.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-07-2018 02:35 AM
Is that because the ACL Table.None provides read access to the columns within the Database View, based on the ACLs defined for the underlying tables?
I'm still getting the same "Security constraints" issue. The report works fine if run from the Incident Table and fine if run from the Problem table. This suggests to me that the issue lies with one or more fields in the Database View itself.
I've checked all the Read ACLs configured on the Incident and Problem tables and there is nothing apart from some with ITIL user restrictions.
Admins can run the report fine. Does the Database View look OK to you?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-07-2018 08:08 AM
The database view looks fine to me. You can unmark the left join on incident.
The only issue I found was the table.*. Because when you add table.*, you will have to start specifying individual field that the role needs access to.
Also if you removed table.*, also add public role to table.None. and do a cache.do and try again.
Please mark this response as correct or helpful if it assisted you with your question.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-09-2018 01:15 AM
All working as designed now. I rebuilt the DB View and ACLs. Adding the specific fields to the DB View was the finishing touch 🙂
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-12-2025 11:14 PM