- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-23-2017 07:35 AM
Hello all,
Today, a strange idea visited my mind: to export a table from one Helsinki Instance to another Helsinki Instance via a XML file.
I made two tests, in order to achieve this:
- Test 1 - exported a XML file of a global (default) table (which exists on both the Instances) from the first Instance and then imported the XML file on the second Instance.
In order to notice any changes, before exporting the XML file, I added an additional Table Column to the table, making the column count to 87, while the same table continued to have 86 on the second Instance.
Here are the steps I did:
Instance 1 -> System Definition > Tables > marked the checkbox of the selected table in the Tables list, then right - clicked the Name filed > Export > XML;
Instance 2 -> System definition > Tables > marked the checkbox of the selected table in the Tables list, then right - clicked the Name field > Import XML;
Result: nothing happened. The importation of the file was completed, but yet, the table of Instance 2 continued to have 86 Table columns, not 87 as the table of Instance 1;
- Test 2 - exported a XML file of a table from Instance 1, which table does not exist in Instance 2.
Result: nothing happened after the importation of the file. The table did not appear on the Instance 2;
I have to say that I read the following documents in Wiki:
Exporting Data - Exporting Data - ServiceNow Wiki
Exporting and Importing XML Files - http://wiki.servicenow.com/index.php?title=Exporting_and_Importing_XML_Files#gsc.tab=0
Importing from Another ServiceNow Instance - http://wiki.servicenow.com/index.php?title=Importing_from_Another_ServiceNow_Instance#gsc.tab=0
All of this leads me to the conclusion that I cannot export a table from one Instance and to import it to another one via a XML file.
I can import table records, but cannot import the table itself (if we have a scenario in which the table does not exist in the target instance, where the importation will be happening) or to import its fields (if we are talking about a scenario in which the table exists on both the instances, but the Table Columns count is different).
In order to be absolutely sure in this, I would like to receive an official confirmation of my understandings. Please let me know:
- If I got the things right or I am wrong and I can export and import a table (no matter existing or not) from one Instance to another. If so, then let me know how to do this;
- Confirm to me if the only way for this to happen (importing a whole table or only its fields from one Instance to another) is via an Update Set?
Thank you in advance!
Best Regards,
Georgi Mavrodiev
IT Consultant
Do It Wise
You may visit us in our Web Site: www.doitwise.com
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-23-2017 11:38 AM
Hello Georgi,
Thanks for the details. Sorry, I missed that table already exists on your target instance. In this case, you should have moved the column XML file(i.e record from sys_dictionary) and it would have worked.
However, in this particular use case when it comes to creating table/columns, I would confirm you that the changes need to be migrated via update set.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-23-2017 07:49 AM
Hello Georgi,
In your first use case, you have mentioned that table was created. However, the column was missing. This is the expected behavior.
The reason being the columns are stored in different table i.e dictionary(sys_dictionary) table. So in this case you need to export and import the dictionary changes.
However, I have seen issues around that while doing so. In this case, I would recommend you to capture those changes via update set.
P.S: Exporting and importing data in XML files is commonly used for records created in a development instance that must be migrated with the update sets as part of a migration procedure. Examples of these records include lookup tables, unit test records, and other information required to support production. Typically, this information is only migrated once and the overhead of an import set is not justified.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-23-2017 11:30 AM
Hello Pradeep,
Thank you for replying to my query!
To be honest, via Test 1, I did not create a new table. I simply used a default table, which exists on both the instances.
So, in both Tests I performed - nothing happened, as I wanted.
In your reply you said: "I have seen issues around that while doing so" - do you refer to scenarios in which someone wanted to export the Table Columns of a specific table via XML file and use it to import these columns into another instance?
My main question is: may you surely confirm to me that the only way to move a table with its Table Columns to another instance is via an Update Set, but not a XML file?
Such confirmation will be more than enough for me, to stop looking into this direction
Best Regards,
Georgi Mavrodeiv
IT Consultant
Do IT Wise
You may visit us in our Web Site: www.doitwise.com

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-23-2017 11:38 AM
Hello Georgi,
Thanks for the details. Sorry, I missed that table already exists on your target instance. In this case, you should have moved the column XML file(i.e record from sys_dictionary) and it would have worked.
However, in this particular use case when it comes to creating table/columns, I would confirm you that the changes need to be migrated via update set.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-23-2017 11:42 AM
Hello Pradeep,
Thank you very much for the confirmation and also for letting me know the location of the table, which stores the Table Columns!
(handshake)
Best Regards,
Georgi Mavrodiev
IT Consultant
Do IT Wise
You may visit us in our Web Site: www.doitwise.com