- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-01-2025 11:43 PM
I have a CMDB-extended custom table where I have enabled auditing in the collector dictionary. When I save the form, the record gets saved, but it is saved two or three times. When I check the activities, I see three or two logs. I am not sure why this is happening. I have checked everything, including Flow Designer and business rules. I found that none of the tables have any custom scripts or Flow Designer processes running. What could be causing this issue, and how can I ensure it reflects only once? I track with help of Activates
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-02-2025 12:21 AM
Check any BR with 'current.update()' that could be updating it a second time.
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
‎04-02-2025 12:51 AM
Definitely some business rule or some script is running.
Since your table is extending CMDB, did you check any business rule from parent is running on your child table
Try to debug the business rule using script tracer
Script Tracer and debugging scripts
Also you can enable debug business rule details and once you save you will get to know the list of Business rules which triggered on insert
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
‎04-02-2025 12:51 AM
Definitely some business rule or some script is running.
Since your table is extending CMDB, did you check any business rule from parent is running on your child table
Try to debug the business rule using script tracer
Script Tracer and debugging scripts
Also you can enable debug business rule details and once you save you will get to know the list of Business rules which triggered on insert
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