Using Xrm.WebApi needs you to be careful with the field names and what to use when. Especially, when you are dealing with Lookups.
One of the most common errors you’ll come across is the one like below – “An undeclared property (fieldname you entered) which only has property annotations in the payload but no property value was found in the payload.”
This is confusing as to what needs to be put in while setting the lookup.
If you have done the below, entered the name of the field which is all in small caps –
object[“msdyn_resourcerequirement@odata.bind”] = “/msdyn_resourcerequirements(<Guid>)”;
This will result in the above error!!!
You’ll need to put the Schema name of the lookup field instead and this should solve your problem –
and the code should look like this –
object[“msdyn_ResourceRequirement@odata.bind”] = “/msdyn_resourcerequirements(<Guid>)”;
And this should totally work for you!!
Hope this helps! 🙂
[…] Set Lookups in Xrm.WebApi D365 v9 correctly. Solving ‘Undeclared Property’ error […]
LikeLike
have you any idea how we can store the execution context in the local storage either session storage or index BD
would love to know how to serialise and deserialize this object
LikeLike
That’s an interesting question. I haven’t tried this, I’ll probably try soon and update here.
Hope that’s fine!
LikeLike