Copy A Custom Table From One Instance To Other
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-18-2014 04:00 PM
Is there a way to copy a custom table from one instance to other, without a clone?
The update set with all the relative data was committed but finish with a lot of errors.
We would have to create a new update set that addresses all those errors.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-07-2014 02:23 PM
Hi
XML export and import is safer, no issue with dictionary fields as long as we prefer to keep sys_id to be same across instances. If you don't care about sys_id then you can use Excel/Easy import. There are many ways to bring data of a custom table across instances.
If you would prefer to export custom table as a whole including structure and data then the best bet is XML export and import. In this case make an Initial XML export on the dictionary fields including Collection object and then import table structure. Once table created, export and import data.
XML is more reliable when everything to be copied to target instance.
Thanks
Sashi

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-23-2014 05:56 AM
So how do you get past the transformation part? It wants a destination table, which doesn't exist. How can you copy a table and data to an instance that does not have that table and I don't have to create one with 100 fields?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-23-2014 01:59 PM
Hi
The scenario which I explained is XML export and then import in the target instance. A table which to be deployed in a target instance including structure and data could be done by multiple ways.
1. Use easy export and import. In this case you must have your new table to be in target instance. A table structure could be moved using an Update Set. Once table created, click on Easy import option on table list view and import data. That's one way. In this case you have an update set to move table structure to target table. When we use Easy import a transform map auto created and used to deploy from import set to target table. In easy import since we created Excel from target table structure, transform map auto creates mapping and loads
2. Same as point 1. Use update set to deploy table structure. But create a Data Source to import table periodically. In this case we create an import set and then create a transform map. Use custom or auto mapping to load data.
3. Case 3. This is what I explained in my reply. Export and Import using XML. In this case you have to elevate your Admin role to Security Admin. First from source instance export table structure as XML. Second export table data as XML. Now you have two XML files in hand. Now go to Target table. Elevate Security Admin role from Admin. Right click on any list view. Any list view. Choose last Import option which only takes XML file as input. Select your first XML file which is table structure. In this case you don't have 'custom' table in target instance. Import it. Now it creates a table structure. Then continue same procedure to import back data.
In third case there isn't any transform map. We are importing structure to structure. All data will be imported including sys_ids. Source and Target is exact same table with same structure.
I hope this clarifies how a new table structure data could be imported without a Transform Map and without that table to be there in target instance.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-24-2014 12:53 AM
Thanks for the help
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-24-2014 09:41 AM
This is all good feedback. We have a realtime solution here at Perspectium. Message me if you would like to know more.