- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-04-2024 08:57 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-04-2024 11:20 PM
Hi @Snehal13
There are 2 things
- Table move/ Business Logic : Use Update Set
- Data - Use XML based movement
Best practice
- Make sure complete only required update set.
- Make them in batches
- Linked as parent - child
- Define order of update set movement.
- Do sanity check before you move update set / data.
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.
Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]
****************************************************************************************************************
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-04-2024 10:01 PM
Hi @Snehal13 check below points
- export CSV/Excel and import via import set, (this can also be enhanced with a transform map)
- exporting an XML file and importing into the target instance.
- adding records to an update set via script. ...
- rest API calls.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-07-2024 09:16 PM
Thanks for the notes. I have couple of questions as below
1. How to move related records ?
ex- incident may be related to email records, incident tasks, attachment, KB articles, problems, SLA, comments
ex- case may be related to work order tasks, attachment, KB articles, problems, SLA, comments ?
2. How to ensure X number of records from one source table match X number of record migrate to target table?
3. How to control failure during data migration - how to identify and resume that specific record migration ?
4. Best practice is to manually update sys properties on target instance or move them as part of update sets ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-07-2024 09:16 PM
Thanks for the notes. I have couple of questions as below
1. How to move related records ?
ex- incident may be related to email records, incident tasks, attachment, KB articles, problems, SLA, comments
ex- case may be related to work order tasks, attachment, KB articles, problems, SLA, comments ?
2. How to ensure X number of records from one source table match X number of record migrate to target table?
3. How to control failure during data migration - how to identify and resume that specific record migration ?
4. Best practice is to manually update sys properties on target instance or move them as part of update sets ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-07-2024 09:16 PM
Thanks for the notes. I have couple of questions as below
1. How to move related records ?
ex- incident may be related to email records, incident tasks, attachment, KB articles, problems, SLA, comments
ex- case may be related to work order tasks, attachment, KB articles, problems, SLA, comments
2. How to ensure X number of records from one source table match X number of record migrate to target table?
3. How to control failure during data migration - how to identify and resume that specific record migration ?
4. Best practice is to manually update sys properties on target instance or move them as part of update sets ?
