Set CRM Lookup Value (another Entity) using WebAPI

(0) Share

Report

Posted on by Community Member

I can create a New Entity but I'm trying to create an Entity with the lookup value to another Entity. The code below works until I uncomment out the line to set the lookup value. It always comes back as Bad request.

void Main()
{
using(var webClient = new WebClient()){
    webClient.Credentials = new NetworkCredential("Username", "Password", "Domain");
    webClient.Headers.Add("OData-MaxVersion", "4.0");
    webClient.Headers.Add("OData-Version", "4.0");
    webClient.Headers.Add("accept", "application/json");
    webClient.Headers.Add("Content-Type","application/json");
    webClient.Headers.Add("Prefer", "odata.include-annotations=*");

    webClient.BaseAddress = "dev.company.com/.../v8.0";

    var JO = new JObject();
    JO.Add("col_name","My Name");
    //JO.Add("col_contactid@odata.bind","/contacts(7266f26b-7105-e611-811e-005056b61789)");
    var dataString = JO.ToString();

    var responseString = webClient.UploadString("col_advisors", "POST", dataString);

    Console.WriteLine(webClient.ResponseHeaders.Get("OData-EntityId"));
}
}

*This post is locked for comments

I have the same question (0)

All responses (6)

Answers (0)

Suggested answer

Brad Sprigg 985 on at

Like (1)

Report
Copy link

Link copied!

Make sure you get the capitalisation of the navigation property correct, I was scratching my head over a similar issue until I dumped the metadata of an entity out to the console and realised that the navigation property of my custom lookup field wasn't all lower case. I would suggest trying the capitalisation listed in the properties of the field first of all.

Was this reply helpful? Yes No
Inogic 748 on at

Like (2)

Report
Copy link

Link copied!

The issue seems to be because of the “col_contactid” name used to set the lookup field. As for Setting lookups of the Custom Entity or setting lookups on Custom Entity you need to specify the <NavigationProperty Name= “”>. You may get it by downloading the OData Metadata from the Developer Resources and search for the attribute name i.e. “col_contactid”. Verify the NavigationProperty Name and the name used in the code. They should match.

Thanks,

Sam

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

I got it to work. The fields really have to be unique as it is case sensitive. Comments here and also this blog, really helped.

inogic.com/.../set-values-of-all-data-types-using-web-api-in-dynamics-crm

Step 1 : Goto Cutomization  Developer Resource. Step 2 : Click to “Download Odata Metadata” link and Download the same. Step 3 : Once Download, open it and find out name of lookup attribute ( i.e. “new_qualifiedleadid”) and check its casing. Step 4 : Verify it with the value which you are setting in the code it should be same.

While my column was "col_contactid", CRM renames the Navigational Column to be what was above "col_ContactId".

I also used Postman(google chrome) plugin and added the following Header to my Post.

webClient.Headers.Add("Prefer", "odata.include-annotations=*");

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Thanks, Your blog really helped. Working on setting up an Online CRM environment so I can post examples on Getting, Updating, Deleting and updating Entities through WebAPI for other people as well.

Was this reply helpful? Yes No
Aishwarya 36 on at

Like (0)

Report
Copy link

Link copied!

I followed the steps as said

"Step 1 : Goto Cutomization  Developer Resource. Step 2 : Click to “Download Odata Metadata” link and Download the same. Step 3 : Once Download, open it and find out name of lookup attribute ( i.e. “new_qualifiedleadid”) and check its casing. Step 4 : Verify it with the value which you are setting in the code it should be same.

While my column was "col_contactid", CRM renames the Navigational Column to be what was above "col_ContactId".

I also used Postman(google chrome) plugin and added the following Header to my Post.

webClient.Headers.Add("Prefer", "odata.include-annotations=*");"

But I am getting an error ""')' or ',' expected at position 8 in (XXX-Guid)"

Is there any different way to pass the value?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

contactid is a managed field, so you wouldn't have your publisher prefix on it. Try "contactid@odata.bind" and see if that works

Was this reply helpful? Yes No