bipinshan / CustomNTONPCFMultiselectLookup

CustomNTONPCFMultiselectLookup
MIT License
2 stars 2 forks source link

POST to create intersect entity record not considering schema name capitalization #5

Open stevenfayers opened 2 years ago

stevenfayers commented 2 years ago

When the POST to create the intersect entity record is initiated, the script fails.

An undeclared property 'aaa_opportunityproduct' which only has property annotations in the payload but no property value was found in the payload.

The payload that the solution tried to post was {"aaa_opportunityproduct@odata.bind":"/aaaopportunityproducts(0561b2d3-51ce-ec11-a7b5-0022489d246a)","aaacountry@odata.bind":"/aaa_countries(625b02d9-92fc-e911-a813-000d3ab5549a)"}

The payload that is needed is (tried in Postman): {"aaa_OpportunityProduct@odata.bind":"/aaaopportunityproducts(0561b2d3-51ce-ec11-a7b5-0022489d246a)","aaaCountry@odata.bind":"/aaa_countries(625b02d9-92fc-e911-a813-000d3ab5549a)"}

For lookups Microsoft requires that that attribute schema name is used before the @odata.bind, which can have case differences from the normal attribute name

stevenfayers commented 2 years ago

If I change the intersect entity main entity look to aaa_OpportunityProduct then on the form load there's a failure:

Could not find a property named '_aaa_OpportunityProduct_value' on type 'Microsoft.Dynamics.CRM.aaa_opportunityproductcountry'.