- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-25-2019 05:11 AM
Hi Experts,
As per my requirement, I have to update more than 1000 CI records in the DEV instance.
For this process, I have done for creating Import set and created a transform map, This process is done successfully in DEV instance.During this process, all the customization's are captured in update set.
issue:When I am going to update this update set in the TEST env. The update set is committed successful. and what ever the transform map I had created, it is also updated.
But After transforming the data, it showing the issue as :Loading with ERROR: and Records in the TEST env. are not updated.
Can u please share your thoughts to, How can I update the TEST env. records with out manual process.
As per my requirement, " CIs from app to cloud class has been migrated without using UI.",:
Because of my client req: I don't have chance to Export all the records in XML and importing in the TEST env.
Is there any other way to move this import set to TEST env.?
Thanks in advance for your time and valuable thoughts...
Thanks
Santhosh.K
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-25-2019 05:16 AM
Import sets are created as part of the Data Source process. They are temporary and don't get captured by the update set, nor do you want them to be part of the update set (it would be like capturing emails that have been sent.) Ensure your have the data source and transform map, then you can install those on your other instances. Start with the data source, ensure the credentials, server (perhaps attachment), etc. are correct for your test system, then load all records. Once they are loaded, then you can transform.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-25-2019 05:16 AM
Import sets are created as part of the Data Source process. They are temporary and don't get captured by the update set, nor do you want them to be part of the update set (it would be like capturing emails that have been sent.) Ensure your have the data source and transform map, then you can install those on your other instances. Start with the data source, ensure the credentials, server (perhaps attachment), etc. are correct for your test system, then load all records. Once they are loaded, then you can transform.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-25-2019 11:44 PM
Hi Chuck,
Thanks for the reply..
As of your suggestion. I had created one new data source and created one transform map, and updated the records in my current(DEV) instance.
As of now in my DEV instance it's updated all the records. And each and every thing, I have captured in update set(like, data source creation, and transform map creation).
Clarification: For moving this customization in to TEST env. do we need to do any pre-activities in TEST env., or else, shall I directly commit the captured update set from from DEV to TEST?
Can you Please confirm....
Again thanks for your valuable suggestion. and time.
Thanks
Santhosh.K

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-25-2019 05:18 AM
Hi Santosh,
what is that error , did you save excel file type 97-2003 work book.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-26-2019 12:01 AM
Hi Santosh,
I would like to suggest you
capture the data data source,scripts and field maps etc.
and then move the update set to test env.
Now upload data using same data source on dev, as you said it has been created successfully.
I don't know why you don't have access to export using XML,but export it using XML,so it will capture imported data with same sys_id,and then import it on test env. using same data source you will get the records with same sys_id.
because the task through update set we can not do.
varsha