Error on the Incident Form

Sudiksha Misra
Tera Contributor

Hello, 

 

Can someone please help me understand this error that comes on the incident. It does not hinder the resolution process of the incident but still appears. 

 

Regards, 
Sudiksha Misra

 

4 REPLIES 4

Weird
Mega Sage

You have something that queries the live_message table and you get that error to let you know that you're missing something because the user doesn't have read access to chat_message and state fields on that field.
Imagine having a reference field where the user doesn't have read access to the data. The field can be populated, but the user doesn't see the data.

You can get rid of the error by modifying property "glide.db.encoded_query.field_acl_error_msg" to false, but note that it affects every similar query, so if something doesn't work people might have to work harder to figure out why.

Amit Pandey
Kilo Sage

Hi @Sudiksha Misra 

 

You had better to remove the live_message field or change the ACL for that particular field from the form layout.

 

Regards,

Amit

Soni Tushar
Tera Guru

Hello @Sudiksha Misra ,

 

Part of the query on live_message has been ignored because of read security rules on 'live_message.chat_message'  OR 'live_message.state'

 

Reason : Why This Happens - ServiceNow enforces security rules to restrict access to sensitive data. If a query tries to access fields or records that the user doesn’t have permission to view, those parts of the query are ignored. This results in incomplete data being fetched, which can trigger this warning.

 

Solution -
Review Security Rules: review the read ACLs for the live_message table, specifically for chat_message and state fields.
Check User Roles: Verify User Roles> Confirm that the users encountering the error have the correct roles and permissions needed to access the live_message table and its fields

Script: Look at any Business Rules, Script Includes, or other scripts that interact with the live_message table. Ensure they are not attempting to access restricted fields or records inappropriately.

 

If you found my response helpful, please consider marking it as "Helpful" or "Accept Solution." Thank you!

 

Dnyaneshwaree
Mega Sage

Hello @Sudiksha Misra ,

Your issue is similar to the issue i have just saw in other post-  https://www.servicenow.com/community/developer-forum/acl-error-after-upgrade/m-p/3001967#M1133620
Check your ACLs on that particular field. And verify for upgrade issues.


Please accept my solution if it works for you and thumps up to mark it as helpful.
Thank you!!

Dnyaneshwaree Satpute
Tera Guru