import/ export tables from DEV to Prod

[sonita]

I have created two tables in DEV instance which I'm trying to bring to prod , what I normally do is to export the table from DEV and import it to Prod. BUT It didn't work now. actually when I imported , the label of the table was label and the data was not inside it and when I tried to show list   , it said this table does not exist!

I'm not sure what is happening!

we had a clone recently , can it be the reason maybe?!

[sonita]

I see, so maybe i should first move my update set and then do the import/ export . Thanks

[JusCuz]

Cool, I definitely recommend reviewing the link I posted above about update sets. Also, I'm not seeing the link for it in that article, but there is an article out there for update set best practices. If you google for that it shouldn't be too difficult to find.

[sonita]

Thank you everyone. it's working perfectly now

[Chuck Tomasi · Accepted solution]

Here are a few more links that may be helpful:

Update Sets Best Practices - ServiceNow Wiki

Getting Started with Update Sets - ServiceNow Wiki

Exporting and Importing XML Files - ServiceNow Wiki

In short, yes - create a local update set, make your changes to the table (create, modify, etc.) and it is all recorded in the update set. When you bring the update set over to the other instance (usually via an Update source) and commit it, you're table is created. From there you can export/import the data that goes in that table.

[bobbymcgill]

Hi Chuck, sorry to resurrect a solved question, but I have a similar situation.

Our group (probably me) made some changes to a few of the base tables. We added 2 fields to cmdb_ci in our DEV instance, and are trying to get it into our integration and testing instance.

Biggest problem is that the changes were made outside of a new update set, and are part of the Default Global space.

Is there any way to capture the additions of the fields in an update set now?