Available for User criteria is not working for the catalog item.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-13-2024 12:04 AM
I have created a user criteria and added in available for section in catalog item to restrict the user but when i migrate the update set to the my PROD instance then users who are not supposed to see the catalog item that users also can see that item on PROD.
How can i fix this??
I have tested for the same users but result is different for the different instance, why so..?
And can we export and import xml file for the Available for to the PROD instance to avoid manually work??
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-13-2024 12:21 AM
You can export/import the xml, but to have version control, I would just use update sets (xml imports can't be traced). Before you do it, you will need to check on the differences between the instances. Mainly: where does your user criteria look at? And is that the same for the user on both instances?
Next to that: is the item the same on PROD as non PROD? Does it have 'not available for' as well on non PROD and not on PROD?
Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-13-2024 12:23 AM
Hi @Mayur ,
Can you verify once using user criteria diagonstics to see whats happening?
Thank you,
Hemanth
Certified Technical Architect (CTA), ServiceNow MVP 2024, 2025
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-13-2024 04:40 AM
Step 1: Compare user criteria configuration and user roles between the instances. Use user criteria diagnostics. Adjust the configuration as needed.
Step 2: If you could not identify any misconfiguration, have the user log out from the instance and log in again. Check if the issue persists or not.
Step 3: If nothing else helps, try clearing the server cache using the cache.do command. (Make sure you do it outside of peak hours as it has a temporary impact on performance.)
Blog: https://sys.properties | Telegram: https://t.me/sys_properties | LinkedIn: https://www.linkedin.com/in/slava-savitsky/