Why priority field is not updating value on Security Incident when updating through flow designer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-06-2025 02:30 AM
Hello Everyone,
I'm investigating an issue where the priority field on a Security Incident Record (SIR) isn't updating after a flow runs, despite successful execution. I'm considering the following potential factors that might be influencing this behavior:
- Are there any client scripts that might be overriding or preventing the priority field update?
- Could any business rules, especially those triggered before insert or update, be interfering with the priority field update?
- Are there any UI policies or field-level security settings that might be restricting the priority field update?
- Is there any other configuration, such as a data policy or a workflow, that could be impacting the priority field update?
Any thoughts or insights on how these factors might be contributing to the issue would be helpful.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-06-2025 05:55 AM
Hello @Yamsanibhavani
You've already identified some key areas to investigate start looking in by checking priority field in scripts sections and see if any of script is overriding.
Also, see if any data lookup definitions are created?
Check the flow properties Run As are set to System Admin I believe if not then do change it and check again.
If my response has helped you hit helpful button and if your concern is solved do mark my response as correct.
Thanks & Regards
Viraj Hudlikar.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-06-2025 06:17 AM
You are updating the priority from the flow desginer that means you are updating at a server level. So you should be investigate accordingly.
1. Surely you should be looking at business rules data policy, other flow/workflows as well.
2. There is quick check that you can do is, check the history if priority field. If the fileld is updating from flow you should be able to history from the same. and you can check if there is something that is changing the priority after this update.
Kindly mark the answer ✔️ Correct or Helpful ✔️ If it addresses your concern.
Regards,
Siddhesh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-07-2025 01:52 AM
Hi @Siddhesh Gawade ,
I have checked why it is not updating is due to dictionary override to default value 4. Is there any possibility still to update the priority field other than making dictionary override to false?
if yes, suggest the way to implement.
Thanks for your reply
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-07-2025 02:03 AM
dictionary override default value only works for new record during creation.
If you are setting the value then your logic should override the default value
Are you trying to insert new record or update?
what's the flow doing?
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