Updating Variable Allocation Accounts
One thing you can check is to send the map to file and open up one of the xml files it generates. You should see a field inside there that has a tag of UpdateIfExists and the value inside of that should be 1.
That would ensure that we are actually passing the update flag through. Which node are you mapping for the process as there is the main create update account node and then there is also a create variable allocation account node. I have not ran through an allocation account map for a while so I will have to check which one should be used for updates unless someone else on here can chip in before then.
I checked the updateifexists flag and it is set to 1. I have mapped the Create/Update Account and Add Variable Allocation Detail nodes.
I did some checking with Microsoft and the updateifexists flag is not used in that procedure. Basically it has to be a new account.
You can submit an issue to Microsoft for them to fix that procedure or we could write a custom node using Node builder that would accomplish the same functionality.
That creates a problem for me….it works in Integration Manager.
That would be because they use a macro and Microsoft didn't create the eConnect the procedure to work the same.
Where did you find this info…online?
We ran through a couple SQL traces with the flag set and not set and it is being passed into the procedure however the statement always tries to insert rather than ever run through an update statement. We then asked someone with access to it whether that was the case or not and they were able to confirm the procedure doesn't actually use the update if exists parameter, the steps Lorren gave above are still your options now.
If you would like to submit an answer or comment, please sign in to the eOne portal.