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?

[Dr Atul G- LNG]

Hi @iamkurt 

400 records are not much , so xml import will work. 

[iamkurt]

@Dr Atul G- LNG- Are you sure?

[Dr Atul G- LNG]

Yes, mate, I have experience migrating 1,000 records at once. But one thing to keep in mind before moving data is to ensure that all reference fields are available so the data gets stored successfully.  @iamkurt 

[jcmings]

Exporting to XML is your best bet. But you raise a good concern -- will the references be broken? For instance, if there is a reference to a user that does not exist, that field on the record in the higher environment will have an erroneous/blank value. Assuming the records themselves have references to other records that are also being imported, you shouldn't need to worry about broken records, since the sys_id's will persist.

Why don't you try with a handful of records and see what's happening from there? Then, you'll know what needs to be fixed for the remaining ~400.