[BUG] - Linking records in a 2-way lookup (one-to-one)

[vmjelde]

We have 2 objects with a lookup field to eachother:

• Object: CartItem, field: Application__c
• Object: Application__c, field: CartItem__c

How can we insert CartItems and Application with both these fields populated?
Can we run insert CartItem, Insert Application, update Cart Item? Or does sfdmu check two-way-lookups (dependencies) and handles it?

[hknokh]

Hello,
You can simply put to Insert the both objects.
Typically the sfdmu handles 2 way dependencies ootb

[vmjelde]

Hello,
Thank you for quick response.

It's great that sfdmu handles 2 way dependencies ootb, but do you have some guidance for it? I tried with two custom objects, but got "Missing expected parent ExternalID value".
See attached .zip for the dataset and logs.

test-data.zip

[hknokh2]

Hello,

Sorry for the delay. I'm still investigating this issue. However, one thing I can say is that for the Upsert operation, you need to specify the name of the external ID field in the export.json file for the object. Additionally, you should include a column in the CSV file for the external ID field value. Otherwise, the plugin will not be able to bind the objects.

For the Insert operation, setting the Id field as the external ID is sufficient. If you set the operation to Insert instead of Upsert, your export.json should work.

I will need to confirm whether this works for the CSV file as well and whether there are any bugs. I will update you as soon as I have more information.

[hknokh2]

@vmjelde
There was a bug of handling circular references, which is fixed.
Please update the Plugin.
Also see the new article regarding your example:
https://help.sfdmu.com/examples/configuration/basic-examples

Note, that it is not possible to upsert or update records using the same CSV files since you would need to set the external ID field in the export JSON file and provide explicit external ID values for each record, which would require different CSV files.
Therefore, for your use case, it is recommended to use Insert instead of Upsert in the export.json.

[github-actions]

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]

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.