Find your people. Pick a challenge. Ship something real. The CreatorCon Hackathon is coming to the Community Pavilion for one epic night. Every skill level, every role welcome. Join us on May 5th and learn more here.

Moving CMDB Data Certification Policies between instances.

Marc Schlank1
Tera Contributor

I created 9 CMDB Data Certification Policies in a lower environment of Zurich to test the process in Data Manager, CMDB Workspace. 

What is the process to move/copy/export these 9 CMDB Data Certification Policies to a Production environment.  XML?  Update Sets?

Please advise. 

3 REPLIES 3

pavani_paluri
Tera Guru

Hi @Marc Schlank1 ,

 

In ServiceNow, CMDB Data Certification Policies are application records, so the right way to move them from a lower environment (like Zurich) to Production is through Update Sets rather than raw XML export.


Recommended Approach: Update Sets
1. Create an Update Set in your lower environment.
2. Capture the Policies: As you create or modify each CMDB Data Certification Policy, make sure those changes are tracked in the Update Set.
3. Complete the Update Set once all 9 policies are included.
4. Export the Update Set as XML (this is the supported export format for Update Sets).
5. Import into Production: Upload the XML file into your Production environment.
6. Preview & Commit: Always preview the Update Set first to check for conflicts, then commit it to apply the policies.


Things to Watch
Dependencies: If your policies reference custom tables, fields, or scripts, make sure those are also included in the Update Set.
Testing: Test the Update Set in a staging/UAT environment before committing to Production.
Baseline vs. Customization: If you’ve customized baseline Data Certification logic, document those changes carefully so they don’t overwrite Production unintentionally.

 

Mark it helpful if this helps you to understand. Accept solution if this give you the answer you're looking for
Kind Regards,
Pavani P

 

Marc Schlank1
Tera Contributor

Thanks, but I'm getting a few different from that suggestion:

 

Being suggested to Export a few tables to XML, Not the Update set path.   Hhhmmm

 

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1647869

 

Recommended Transport Mechanisms

Instead of Update Sets alone, use:

  • Configuration Data / Instance Data Replication
  • Manual export/import of:
    • sn_cmdb_ws_dm_certification_policy
    • cmdb_data_management_policy_runtime_attributes

Update Sets alone are not reliable for CMDB Data Certification policies

Tony Branton
ServiceNow Employee

Currently there's an issue with exporting and importing Data Manager policies between instances via an update set.  A Data Manager policy consists of a record in the sn_cmdb_ws_dm_certification_policy table as well as a related record in the cmdb_data_management_policy_runtime_attributes table.  An update sets will pick up the policy record but not the related runtime attributes record.

The impact is that when you apply the update set in a target instance, the policy record will be imported but will not appear in the Data Manager policy list in CMDB Workspace as it relies on the related runtime attributes. 

We are working on a fix, however we also want to have any exported policy imported in a draft state (importing a published policy can lead to issues if any referenced records don't exist in the target instance).  A fix for the update set issue is planned for a forthcoming release of CMDB Workspace.