Hide Request Price in service workspace
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi,
Is it possible to hide price on service operations workspace without configure ui builder or changing requestInfo SNC script include?
Thanks,
Tomer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
without UI builder config or script change not possible.
you might have to duplicate that Record Information and then make changes
check this
Service Operations Workspace - Configuration
OR
Another way is to use field level READ ACL on Price field on REQ and ensure it's seen only for the users you want.
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Thank you for marking my response as helpful.
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @tpeleg ,
Hiding the Price field in sow without touching UI Builder or core script include is tough but partly possible.....price, quantity these are often coming from the RequestInfo / RequestInfoSNC script includes or via static form header or formatter macros that are read only,.....so you can’t just remove them globally unless you clone or override things, but you can get around it by using a Workspace Form Header record for your table and removing Price/Quantity from the secondary field list, or using audience/user criteria to hide those fields for certain roles, but if those values are hardcoded in a formatter or macro you’ll likely need a minimal customization....
If you found my response helpful, please mark it as ‘Accept as Solution’ and ‘Helpful’. This helps other community members find the right answer more easily and supports the community.
Kaushal Kumar Jha - ServiceNow Consultant - Lets connect on Linkedin: https://www.linkedin.com/in/kaushalkrjha/