Unable to see dot-walked fields in reporting dashboard
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-08-2022 06:39 PM
Hi
I have an issue where a user can't see any fields that are dot-walked in a report from the dashboard. The particular field is in the grouped by. However if the field is removed from the grouped by and replaced with a field that is not dot-walked, then the user is able to see the report.
- Labels:
-
Analytics and Reports
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-02-2022 12:25 PM
Having the same issue here. User can see the dot-walked field in the record itself, but not in the report. So when we group on the dot-walked field, we get security constraints. However, if we remove the group by, the report works but the dot-walked field in the report is blank (but if we open the record we can see it).

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-02-2022 12:38 PM
Hi,
Did you check the report_view ACL on that particular table?
Regards,
Deepankar Mathur
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-03-2023 08:12 AM
Same here. Report generated in the sc_task_sla table. When trying to retrieve the fields from the request item through dot walking they remain not populated. User can see these fields in list and inside the record but not in the report, so it is not ACL related. I as an admin can see them though. Any inputs if this is really a bug? We are in San Diego moving soon to Utah. Thanks in advance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-30-2023 09:34 AM - edited 06-30-2023 10:54 AM
I suspect your problem is due to KB0827368-Dot Walked fields are not showing value on the List layout but visible on Form.
The user running the Dashboard/Report is not being given read access to the dot-walked data via a Role but instead via information on the dot-walked record itself. For performance reasons, ServiceNow does not pull all the data from dot-walked records -- just the specific fields that have been dot-walked. However, that means that the ACLs on those dot-walked Tables that evaluate based on information on the dot walked Table will not evaluate as 'true' unless that necessary data is included as one of the dot-walked values.
eg.
- Let's say there are two Read ACL that allows user to see INC:
- User has the "incident_read" Role
- User is listed in the "Opened by [opened_by]" field
- A Report exists for SLAs that dot-walks to the INC to display the INC's "Short description [short_description]"
- A user with the "incident_read" Role would be able to view that Report of SLAs and see the INC's "Short description"
- However, a user who does not have the "incident_read" Role would not be able to view the INC's "Short description" when reviewing the SLA Report, even if the INC has them as the "Opened by", as the ACL to evaluate if the user is permitted to see that data does not have access to the INC's "Opened by" data to evaluate.
- If the SLA report is updated to include the INC's "Opened by", that user will now be able to see the "Short description" as the ACL now has that information to evaluate.
You can create a scripted ACL to do glide lookups to get around this limitation but I would be very wary of performance issues that this approach will very likely incur.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-30-2023 10:53 AM - edited 04-02-2025 06:30 AM
[somehow my comment was duplicated but I cannot delete this]