Report ACL - unable to view dot walked columns
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-17-2016 06:21 AM
I have a client who's Incident form has a reference field to the kb_knowledge table.
One of the users has many roles, and among which are itil, knowledge_admin and report_admin. She is able to run a report on the knowledge table and see the data (e.g. Short Description) without issue. The problem I am trying to fix is that when she runs a report on the Incident table, and adds columns by dot-walking to the knowledge table through the Knowledge Article reference field on the Incident form, she can't see the data. She is able to add the columns without issue, but all the columns are empty.
I enabled the security debugger, and impersonated the user, whichconfirmed that the user does have "report_on" ACL access to the Knowledge table.
Note: as admin, I have not issues viewing the columns. so it seems pretty likely that it is an ACL issue.
Here are screenshots to show what I am talking about:
Dot walking from Incident, the fields are blank.
Directly from the knowledge table, they are not blank:

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-17-2016 01:32 PM
Can you screen shot the ACL?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-17-2016 01:40 PM
which ACL, and for which table?
I have not put any specific ACLs in place to try to make this work, this is strictly OOTB.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-17-2016 03:07 PM
'the user does have "report_on" ACL' - I don't see one out of the box, was thinking you created this?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-17-2016 04:31 PM
Well, if the user is able to create/run reports off the kb_knowledge table and the incident table, doesn't that confirm that the lack of a specified report_on ACL is irrelevant?
Aside from that, I just tested the same scenario in my own dev environment, and didn't have any issue. I guess I'll have to contact support to see what might be wrong...