Easiest way to promote 400 records from a lower env to higher env

[iamkurt]

I need to create some 400 software models. I am thinking of creating an import set (custom table, data source and transform map) on cmdb_software_product_model table to upload all these in 1 go.

1. If I upload the 400 models usinf import set, one way is to export XML and just import it into higher env. That's probably the easiest thing to do. However, someone told me that "There are a lot of references to other records on these imports, and if you migrate via xml it will break a lot of the relationships (unless you've just done a recent clone of PROD)". So just wanted to confirm with the rest of the folks here if exporting and importing XML is wrong way of doing things.

2. I tried adding the custom table which was created and the transform map to an update set and promoted the update set to a higher env. The custom tabel has name "label" in it and does not seem to go away. In my case, I am not even able to open the custom table. I get "The page you are looking for could not be found." when I try to open it. On sys_db_object, when I open the record for this table, and go to Related Lists → "Labels" tab, and update the Label and Plural form there, nothing happens. I have seen others report the same issue since years but there is no resolution -

A) https://www.servicenow.com/community/developer-forum/table-label-is-showing-as-label-for-extendend-t...

B) https://www.servicenow.com/community/developer-forum/table-label-showing-label-instead-of-table-name...

C) https://www.servicenow.com/community/developer-forum/table-label-is-showing-as-label-instead-of-actu...

D) https://www.servicenow.com/community/service-management-forum/renaming-a-table-name-after-creation/m...

My question is - is it safe to go with exporting and importing XML to higher env, since that will be easiest for me? Or do I have to go with Import Set wrapped in Update Sets route?

[iamkurt]

@jcmings- Thanks, generally , what is considered safer? XML import or import sets promoted using update sets? Asking coz I have been working hard at import sets since a week now.

[jcmings]

I think you're going to run into the same scenario with potential broken references, regardless of whether you do XML import or an update set. XML imports are certainly easier to do -- they take less manual steps. (Only like two actions -- export and then import.) All that to say... I don't know that an XML import is any more "unsafe" than an import set.

[Juhi Poddar]

Hello @iamkurt 

Go with Exporting & Importing XML if:

• The target instance is a recent clone of the source.
• All referenced records (e.g., manufacturers, vendors) already exist in the target instance.
• You want to retain sys_ids and ensure an exact copy of the data.

Considerations before using XML import:

• If the target is not a recent clone, referenced records may be missing, causing broken relationships.
• To avoid this, import referenced records first before importing the XML.

Hope this helps!

"If you found my answer helpful, please like and mark it as an "accepted solution". It helps future readers to locate the solution easily and supports the community!"

Thank You
Juhi Poddar