[QUESTION] - Unable to copy external object references

[akingumusel]

Environment

We are trying to migrate data between 2 orgs (Org A to Org B). Both orgs are connected to the same 3rd org (Org C), which is connected with the Salesforce Connector from Org A and B. Certain objects are exposed as external objects. Account object in Org A and Org B has external lookup to object in Org C.

Issue When we are trying to migrate the Account object. Somehow the external lookup values are not copied over. We tried using "all" multiselect or specifying the external lookup API name directly. When we check the logs, actually the tool queries the external object to find the records, and reports that 1 record is found. But the field is left null in Org B after the migration.

We tried various simulation methods to do a simple regex replacement with useValueMapping, where we tried to do any match (.+) and replace it with $1, since the external reference id will be same in both orgs, to carry it over as is. But still the generated CSV contains no values.

Not sure what the problem is. Will appreciate if you can help.

[hknokh]

Hello, @akingumusel

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

[akingumusel]

So I debugged through a test run. What I observed as the problems are:

• The value mapping functionality is actually run after the lookup field values are updated. So if it is not able to find same record in the target org, it sets the value of lookup in "cloned" to null. Hence the regex does not apply anymore.
• The external lookup behaves a little bit weird in the org. The external lookup value starts with "a". But when you query the external object, the id of the same record starts with "x". Hence it is not able to find the match.

[akingumusel]

Update from my end:

• I actually did a quick dirty fix in ___updateLookupIdFields() method, where I just copy the value from the source if the parent object is an external object.
• What probably makes sense is to refactor the task setup so that
  • if the object is an external object type, then include ExternalId fieldinto the fields to retrieve, similar to Idfield.
  • in setExternalIdMap() method, use the ExternalId as key while constructing idRecordsMap in sourceData.

[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.