Hi,
I have a DEV and PROD environments.
I created a simple Dataflow in the PROD environment, that copies accounts from DEV to PROD. Since this is meant to be a one-time action, I chose "Append" (and not "Merge") as the Dataflow type, and therefore wasn't asked to choose a key column.
After the accounts were created I wanted to delete one of them from PROD but got an error message saying: "Record Is Unavailable" / "The requested record was not found". When I downloaded the log file for the error I saw a similar error: "Entity 'Account' With Id = 289bcf83-a4e6-ec11-bb3c-000d3a319449 Does Not Exist". The surprising part for me is that the mentioned account id wasn't the id of the account I was trying to delete (as shown in the url), but instead it was the id of the matching account in DEV!
This happened in the front-end UI, but even when I tried deleting a (any) record from the maker portal - I still wasn't able to do it.
In the screenshot you can see the GUID in the error message isn't the same as the GUID of the record itself. Once again, the GUID in the error message is actually the GUID of the original (matching) account in the source (DEV) environment!
Of course, I need help deleting these records, but I would also appreciate an explanation of what's going on here. I know that if I select MERGE for the Dataflow type and then select the correct unique primary key - that should preserve the GUIDs between the source and the destination, but I chose APPEND and new GUIDs were created for the accounts in PROD. How come the old GUIDs are still referenced anywhere in the destination environment?!
Thanks so much!
Gil.
94
Share
Report
All responses (
Answers (
