[QUESTION] - Field Mapping is not working for ID field

[ruqianq]

This question is related to https://github.com/forcedotcom/SFDX-Data-Move-Utility/issues/282, even though it marked as closed, but I dont see the confirmation.
I am trying to do the same load the legacy id into target org on different field under the same object. I am using simple insert operation, no need to do comparison. However, the legacy id field would got override by the ID. Apparently it start with the insert, then conduct an update, dont know why this is happening. Here is my code:

{ "operation": "Insert", "useFieldMapping": true, "query": "select Description, Fax, Id, Name, Phone, ParentId from Account" }

fieldMapping.csv ObjectName,FieldName,Target Account,,Account Account,Id,Legacy_Id__c

[hknokh]

Hello, @ruqianq

Thank you for reaching out. I will do my best to assist you as quickly as possible and will keep you updated on my progress.

Cheers

[ruqianq]

Hi I think I found out the root cause, and in fact my query miss one field 'ParentId' somehow that trigger the update after insert.

[hknokh2]

Hello,

• You can find a detailed response about using an external ID with field mapping in this article: Fields Mapping: Mapping External ID Field. Generally, map the external ID carefully; the source and target fields for the external ID should exist in both orgs. You can also remove the external ID from the mapping schema and try other transformation options if you want to just back up the old external ID elsewhere in the target org.
• I assume that your field mapping schema is in the export.json file, not as an external CSV file, since it will not work otherwise.
• Make sure that your fields in the query string are case-sensitive, as this is mandatory for proper field mapping.
• The update is also triggered since you've included "ParentId" in your query string, and it might reference the same records that you are trying to insert into the target. This involves an update phase. Normally, when you try to insert lookup fields, it always performs both insert and update operations to ensure that all related lookups are populated.

I hope this helps. Please let me know if you need further assistance.

Regards.

[hknokh2]

By the way, I highly recommend using my SFDMU GUI Desktop App. It can really help you with configuring field mapping, creating and managing your export.json file, and launching jobs in general.

[ruqianq]

Thanks for the explanation, this is helpful. I have refactored my code, first job to conduct the insert first to populate the legacy id then the 2nd job to update the record with the parent id.

[hknokh2]

Do you use objectSets?

[ruqianq]

correct

[github-actions[bot]]

This case has been marked as 'to-be-closed', since it has no activity for the 3 days.
It will be automatically closed in another 3 days of inactivity.

[github-actions[bot]]

This case has been closed, since it has no activity for the last 6 days. Feel free to reopen it, if you need more help.