Cannot view "sys_created_by" on the sp_log list?

xiaix · ‎08-03-2023

I tried every which way to show sys_created_by as a column on the sys_log list. To no avail.

First, when I click on the gear for "Personalize List", I don't even see sys_created_by as an option:

Ok, let me try to force feed it on the sys_ui_list record:

Welp, even that didn't work 😞

Here's the messed up part... I can query it in a background script:

So, it's there... so why can't I get it to show on the list view??

sushantmalsure · ‎08-03-2023

This happens because of ACL created on sp_log.sys_created_by.

There is OOB ACL to do restrict the read operation

https://<instancename>.service-now.com/sys_security_acl.do?sys_id=6aec9a655302111066c1ddeeff7b1288

This is meant to be not seen by any body including admin (admin override is false).

Try modifying it as per need

If my answer has helped with your question, please mark my answer as accepted solution and give a thumb up.
Regards,Sushant Malsure

View solution in original post

MG Casey · ‎02-01-2024

Anyone know why the OOB ACL is set this way? That seems like a valuable field to be able to report on.

Jay Gamblin · ‎03-22-2024

Happened in Utah upgrade. See release notes: https://docs.servicenow.com/bundle/utah-sandiego-df3/page/release-notes/rn-combined/utah-sandiego/ut...

Increased security by disallowing access to the User (sp_log.user), Created By (sp_log.sys_created_by), and Updated By (sp_log.sys_updated_by) columns of the Service Portal Log Entries [sp_log] table for all users through read and report_view ACLs. Only the security_admin role can give access to these fields.