Share
ReportI'm working with the Web API and have encountered an issue with alternate keys.
Here's the scenario:
Contact entity has an alternate key which is a GUID stored as a text field.
I have a POST message which should add the contact to a lookup using this alternate key:
"djb_contactid@odata.bind": "/contacts(djb_identity_username='00000000...etc')"
however, because the value of the text field is a GUID, the POST request returns the following error:
"code": "0x80040217",
"message": "Contact With Id = 00000000...etc Does Not Exist"
If I attempt a GET with the same key, it works as expected.
GET /api/data/v9.0/contacts(djb_identity_username='00000000...etc')
is this a bug? or some issue with the way its encoded as part of the POST?
*This post is locked for comments
All responses (
Answers (
291,280
