Populated field in a report is exporting as blank

SeanM1
Tera Guru

Hi all, I have what I assume is a simple issue that I just can't work out.

I have a report based on the sc_task table and I have dot walked to the sc_request table to pull in the 'Requested By' field (it's a standard reference type based of the sys_user table)

When I run the report the the fields are populated as expected.

find_real_file.pngfind_real_file.png

But when I export it to excel or pdf the 'Requested By' is blank

find_real_file.png

What am I missing, your help would be appreciated

15 REPLIES 15

Pradeep Sharma
ServiceNow Employee
ServiceNow Employee

Hey Sean,



Thanks for the update. "But when I export it to excel or pdf the 'Requested By' is blank" was hidden between the images


I missed that statement. I will get back to you if I have any update on this.


keepintouch_kir
Giga Contributor

Hello Sean,



Is this issue resolved? If yes, please let us know how it was fixed. We are facing the same in Helsinki version.



Warm Regards,


Kiranmai


Same here, right now I think it may be related to what is talked about here:



Re: User doesn't see data in the exported spreadsheet



but I can't find the right ACL to fix my issue.


Hi, this was never resolved.


This is what I got via HI and it seems to be working with no perceptible performance hit:



This is a known issue addressed in PRB573139.


For temporary relief, create a new property named glide.ui.list.optimize with the following:



type as true/false


value as false



Disclaimer: Adding this system property, with the specified settings, causes a performance impact on the list views and is not specifically recommended as a "workaround."



The main issue is that for dot walked fields, the ACLs are evaluated with a copy of the dot walked record that only contains the fields we are trying to display. If the ACL for some reason attempts to reference another field on that table or is using the current GlideRecord, it will fail to get the value and therefore fail the ACL check. The reason why it is different for admin is that these ACL's likely have "admin overrides" checked and therefore are not evaluated.


Setting this property to false seems to make the system use the entire record instead of the "optimized" one which allows the ACLs to be evaluated correctly.



I believe the issue is occurring due to the below ACL as it is using the current GlideRecord during the read operation.


https://sbprod.service-now.com/nav_to.do?uri=sys_security_acl.do?sys_id=01a565b34f7bba00e52350ee0310...



Known Error Article:


https://hi.service-now.com/kb_view.do?sys_kb_id=a1c6b82f87ffc980491683bdff434d28



You may create the property glide.ui.list.optimize and set it to false as a temporary workaround but I suggest you re-visit the read ACL I mentioned above.



With this information, I'm placing the incident in the Solution proposed state. Please let me know if the above approach resolves the issue.