Hi Iyn,
With one of our customer the below approach worked and i hope this will help you as well:
I was able to edit up the XML file to get it to import to the newly created table in another instance. In my case, we merged 2 custom tables into 1. This may not be best practice, but it's what we had to do to get the records over. For future references, these are the fields that had to be updated in the XML to get the table to match up. Underlined are the table names. I simply did a replace in the XML.
I was able to edit up the XML file to get it to import to the newly created table in another instance. In my case, we merged 2 custom tables into 1. This may not be best practice, but it's what we had to do to get the records over. For future references, these are the fields that had to be updated in the XML to get the table to match up. Underlined are the table names. I simply did a replace in the XML.
**NOTE - I did not do a replace on just the table name because I didn't want to affect the field names, so I made sure to copy the full XML statement I wanted to replace.
EDITS IN XML FILE
<OLD> = <NEW>
<equip_request action="INSERT_OR_UPDATE"> = <u_asset_movement_request action="INSERT_OR_UPDATE">
<sys_class_name>equip_request</sys_class_name> = <sys_class_name>u_asset_movement_request</sys_class_name>
<table_name>equip_request</table_name> = <table_name>u_asset_movement_request</table_name>
</equip_request> = </u_asset_movement_request>
I also did a CSV export/import to capture any other data to connect to the newly created fields.
This may not have been the best solution, but it was a solution that worked for me.
Thnaks,
Adityaa Telidevara
