Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Importing an object with multiple lookup fields to the same source object fails #129

Open
cdevelin opened this issue Jul 9, 2023 · 0 comments

Comments

@cdevelin
Copy link

cdevelin commented Jul 9, 2023

We are importing an object which has multiple fields which are lookups to the same object, but each lookup field is restricted to a different record type of the source object.

E.g. Object B has lookup fields X, Y, Z, which are all records in lookup Object A.

Object B Field X must be a specific record type 'RT X' of object A
Object B Field Y must be a specific record type 'RT Y' of object A
Object B Field Z must be a specific record type 'RT Z' of object A

Object A and B are correctly populated in the source Org, and Object A is extracted first in the data plan, then Object B is extracted, and all the fields in the downloaded data for Object B I can see are correctly mapped to the various reference IDs in Object A.

However, the import often fails for Object B, saying it is trying to insert invalid values into X, Y, or Z. (It can change which field is 'corrupted' during import).

It seems the Texei import routine doesn't keep track of the import fields reliably when there are multiple fields from the same source object being populated simultaneously into the target object.

To be clear, the data-plan is correct, and the data extract is correct, each field in the data extract for Object B is correctly referring to the correct source field in Object A. It is during the load itself that the Texei attempts to insert what I suspect is the 'Z' field value into fields X and Y (or it populated X, then overwrote it when it was populating Y, and then overwrote X and Y when it was populating Z, because they are all from the same source object.).

The error message upon attempted record insert is that the value is illegal in X.

If I remove the mandatory record type filter and allow any value to be inserted into X, then I can see it has been assigned the Z value, even though that was not what was in the data-plan or the extracted data.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant