Set Lookups in Xrm.WebApi D365 v9 correctly
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! 🙂
Related posts:
From Client Secrets to Certificate-Based Authentication: Building a Secure Integration with Azure Ke...
From Multiple Data Sources to Azure Databricks: A Zero-Downtime Power BI Report Data Migration for F...
Using AI for Data Discipline That Drives Better AI Outcomes
