I cannot see a custom field in frontend but it is present in backend
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10 hours ago
Issue:
I created a new reference field (threat_hunting_id referencing to Threat Hunting Table) on the sn_si_incident table. The field is visible to me (as an admin) on both the frontend form and backend (Form Design). However, for other users without the admin role:
- The field is not visible on the frontend form,
- But it is visible in Form Design.
What I’ve tried:
- Checked for UI Policies and Client Scripts → None applied.
- Tried configuring ACLs for the field → No effect.
- Created a new similar reference field to rule out corruption → Same behavior.
Question:
What could be causing this and how can I make the field visible to non-admin users?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 hours ago
Hi Isha,
That’s a good question, Sometimes this type of issue happens due to ACLs or related configurations. You can check this detailed discussion on the ServiceNow Community, it might help you:
Hope this helps!
Thanks & Regards,
Muhammad Iftikhar
If my response helped, please mark it helpful & accept the solution so others can benefit as well.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 hours ago
Simple rule
-> if logged in user doesn't satisfy Table.None READ ACL on the table being referred the field won't be shown on form
-> So check if your user has read access to "Threat Hunting Table"
-> Check Table.None READ ACL on that table and give appropriate role to that person present in roles section
If my response helped please mark it correct and close the thread so that it benefits future readers.
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader