Bulk CI retirement using Transform Map

UshaK5308581747 · 3 weeks ago

Hi All,

I need suggestions on the best approach to retire bulk CI/server records in CMDB. The requirement is to update Operational Status, Installed Status to Retired and also remove the existing relationships when CI retired without modifying system fields.

Currently ,I am trying through transform map like batch-wise, and sometimes the Updated ,Updated By fields are not modifying and sometimes they get updated with the latest date with my name.

I even added sysAutoFields(false) in my script.

Dr Atul G- LNG · 3 weeks ago

“The best and out-of-the-box (OOTB) way is to use the certification task.”

https://www.servicenow.com/docs/r/servicenow-platform/configuration-management-database-cmdb/data-ma...

*************************************************************************************************************
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/dratulgrover [ Connect for 1-1 Session]

****************************************************************************************************************

Its_Azar · 3 weeks ago

Hi there @UshaK5308581747

For retiring CIs and removing relationships, a Fix Script or Background Script is usually cleaner and more reliable than a transform map, especially for bulk operations. You can also disable workflows using setWorkflow(false) during the update to avoid unintended updates to system fields.

☑️ If this helped, please mark it as Helpful or Accept Solution so others can find the answer too.

Kind Regards,
Azar
Serivenow Rising Star ⭐
Developer @ KPMG.

UshaK5308581747 · 3 weeks ago

We need to retire approximately 100k CIs. Can this be achieved using a Fix Script?

Teja R · 3 weeks ago

Hi @UshaK5308581747 ,
Why are using the transform map , you can do this using the Data manager policy.
Regards.