Move custom table from DEV to PROD
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-26-2014 08:19 AM
What's the recommended and easiest way to move a custom created table from DEV to PROD? It did not come over on the update set. On Berlin, by the way.
I assume I can do to u_table.list and export XML? Would I then just create the same table manually in PROD and import the XML? That seems tedious, no?
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-26-2014 08:27 AM
If it didn't come over with the update set, then the record for the creation of it is not part of the update set.
You could create a new update set on DEV and move the records for the table creation manually into it.
Those are normally records with a type of "Dictionary", "Database field(s)" and "Table"
You will need all of them. But read the sys_update_xml records carefully and move only those you really need.
Other option would be to create it manually on PROD and then clone over dEV to sync both instances for future development work.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-26-2014 08:29 AM
The table itself was created in PROD from the update set it seems, but the data in the table did not move over. Is that normal behavior?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-26-2014 08:31 AM
Yes, that is normal behavior. This is to prevent data to be moved to a PROD system.
In case the table contains only configuration settings you might want that and you can activate that.
http://wiki.servicenow.com/index.php?title=Administering_Update_Sets
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-26-2014 08:33 AM
Understood. So then to move the data, it's the standard Export XML on DEV - Import XML on PROD as best practice?