You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am getting an E00039 error in my createCustomerProfile response. This error indicates that a duplicate profile already exists. I understand this error and why is is returned in my request but unfortunately the customerProfileId is not returned in the response. It just has a null value.
If I had the matching customerProfileId returned in the response then I could get the matching profile and continue with my process, or I could delete or edit that profile. How come the customerProfileId is not returned in this instance?
*Note: the customerProfileId is included in the error message "A duplicate record with ID XXXXXXXXXX already exists." I suppose I could parse this message and grab the ID but that seems like an unnecessary hack.
The text was updated successfully, but these errors were encountered:
I ran into this problem implementing the Accept Hosted form and I strongly sympathize. This issue creates a sequence paradox returning customerProfileId, which should be much more accessible. I had to solve it using the error text hack you mentioned.
I am getting an E00039 error in my createCustomerProfile response. This error indicates that a duplicate profile already exists. I understand this error and why is is returned in my request but unfortunately the customerProfileId is not returned in the response. It just has a null value.
If I had the matching customerProfileId returned in the response then I could get the matching profile and continue with my process, or I could delete or edit that profile. How come the customerProfileId is not returned in this instance?
*Note: the customerProfileId is included in the error message "A duplicate record with ID XXXXXXXXXX already exists." I suppose I could parse this message and grab the ID but that seems like an unnecessary hack.
The text was updated successfully, but these errors were encountered: