GlideRecordSecure cannot update HTML field on custom table, but GlideRecord works
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi Community,
We are trying to update an HTML field on a custom table using a script include.
When we use GlideRecord, the update works as expected.
However, when we switch to GlideRecordSecure, the update does not work.
What we have already checked/tried:
Verified ACLs (read/write) on the table and the HTML field
Ensured the integration user has the required roles
Added the integration user to the Conditional Script Writer group
- Verified custom application cross-scope privileges
Despite this, the update only works with GlideRecord and fails with GlideRecordSecure.
This behavior started after our instance was upgraded to the Zurich release. Prior to the upgrade, the same logic was working as expected.
Any guidance would be appreciated.
Thanks in advance!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Definitely access control issue here
how and from where that script is executing?
Is it from some BR etc?
Is your script able to update some other normal field like Choice or String etc using GlideRecordSecure?
💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hello @Ankur Bawiskar
Thanks for checking.
The script is executing from a Business Rule.
Other scripts running in the same context are working as expected.
Using GlideRecordSecure, I’m able to update other normal fields (String / Choice, etc.) without any issues.
However, when updating the HTML field, the update goes through and the images do get attached, but they appear as broken images in the HTML field content.
So the write itself is happening, but something seems to be breaking specifically for HTML/image rendering during the update, not for standard fields.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
you just said the update goes through but images are broken.
It means field is getting updated but user doesn't have create/write access to images table I believe.
hence that issue
Did you check that?
Try giving image_admin role to that API user and see
Check below ACLs for Create and Write (Table.None and Table.*) have that role
💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
@Ankur Bawiskar
For additional context, the integration uploads images to the sys_attachment table and then uses those attachments in the HTML field content. The images render correctly in the activity stream, but appear broken when displayed within the HTML field.
Regards,
Ganesh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
then did you check the HTML source code of that HTML field?
how it shows ? share screenshot
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
