We experience an error during the upgrade of the SF to 2023.1 regarding data mapping.
Is this a known error?
I am cleaning up our current projects and will investigate some more around the related data which could trigger such an error. But if you guys/girls have any clue, please help me.
Best answer by Mark JongelingView original
This looks like a situation in which the data migration has caused an issue, which results in data being present in the target table of the reference, but not in the source table.
We would need to investigate this, could you create a ticket in TCP for this?
I made a ticket in TCP.
We could easily bypass the bug, because we have one domain for all map data objects. I changed the <UPGRADE> update in dom_id, by putting in our domain name in the script. The rest of the upgrade went smoothly.
We have fixed the issue in the Upgrade script, so new Upgrades will not run into this problem 😄