Customer experience | Sales, Customer Insights,...

Unable to set lookup field value using Xrm.WebApi.online.createRecord

(0) Share

Report

Posted on by Vishal Patil

I'm creating new record using Xrm.WebApi.online.createRecord. I'm adding lookup field value while creating record. See my code below. In the code, new_engagementsector is my lookup field name, 'new_sectors' is the name of lookup entity & 'cr0f8_engagements' is my entity name in which i am adding record.

var entity = {};
entity["new_engagementsector@odata.bind"] = "/new_sectors(97511775-8737-ea11-a813-000d3a0a827e)";

Xrm.WebApi.online.createRecord("cr0f8_engagements", entity).then(
function success(result) {
var newEntityId = result.id;
},
function(error) {
Xrm.Utility.alertDialog(error.message);
});

Its giving below error,

An error occurred while validating input parameters: Microsoft.OData.ODataException: An undeclared property 'new_engagementsector' which only has property annotations in the payload but no property value was found in the payload.

Is there anything missing in code? please help.

All responses (3)

Answers (0)

cloflyMao 25,208 on at

Like (0)

Report

RE: Unable to set lookup field value using Xrm.WebApi.online.createRecord

Hi,

To update a lookup field, you should use field schema name.

You can find schema name property in entity > fields.

In most of cases, it will contains some upper case characters.
Suggested answer

Bipin D365 28,981 Moderator on at

Like (0)

Report

RE: Unable to set lookup field value using Xrm.WebApi.online.createRecord

Hello,

You need to use schema name of the field instead of logical name.

entity["SchemaNameofthefield@odata.bind"] = "/new_sectors(97511775-8737-ea11-a813-000d3a0a827e)";

Please check below link.

community.dynamics.com/.../create-record-of-custom-entity-through-web-api
Suggested answer

Naveen Ganeshe 3,393 User Group Leader on at

Like (0)

Report

RE: Unable to set lookup field value using Xrm.WebApi.online.createRecord

Hello Vishal,

Everything looks good but please make sure you are using the schema name for "new_engagementsector" field.