sys_id is different for users but the name is same in other instances
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-21-2024 02:29 AM
The flow is working in the dev instance, but in other instances, the approvers are not triggering in the approval tab because the sys_id is different for the approver person but the name of the person is same in all instances which is impacting the flow.
Is there any solution to avoid this 'sys_id' issue? Please help.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-21-2024 02:31 AM
It means someone created the user manually in another instance instead of migrating from Dev.
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.
Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]
****************************************************************************************************************
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-21-2024 02:48 AM
users are updated from Azure team.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-21-2024 02:46 AM
Hi @Jayashri Sonawa,
Try to avoid hardcoding sys_ids due to this exact issues. ServiceNow doesn't recommend hardcoding sys_ids. If you have no choice then make sure you migrate the update sets from dev instance remotely to higher instances every time.
If you found my reply useful, please mark it as Solution and Helpful. This will help me and the community.
Thanks and Regards,
Ehab
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-21-2024 02:54 AM
A potential workaround would be to use the Lookup Record(s) action to first find the user by their email address (or other unique identifier) within the flow. Once you've found the appropriate user record, you can use them in the Flow for approvals or whatever you require and it will work in whichever instance.
- Matt
