Microsoft Dynamics CRM (Archived)

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

(0) Share

Report

Posted on by kiruthigarani

Even though i'm using the Schema name, we are facing the above error in "tasks"

URL : https://Domain-url/api/data/v9.0/tasks

REQUEST:

{
"description": "Kiruthiga's Task 3",
"subject": "Kiruthiga's task 3 subject",
"statecode": 0,
"actualdurationminutes" : "20",
"regardingobjectid_contact@odata.bind" : "/contacts(contact_id)",
"ownerid@odata.bind" : "/systemusers(user_id)",
"new_lookup_account@odata.bind" : "/accounts(account_id)" // Error throwing for this custom fields

"new_caseassociate@odata.id" : "/incidents(case_id)" // Error throwing for this custom fields

}

2744.tt.png

I have checked my schema name using https://domain_url/api/data/v9.1/EntityDefinitions(task_meta_id)/Attributes?$filter=IsCustomAttribute%20eq%20true

I have tried new_Lookup_Account too,but no luck also it deosn't make sense.Because im using the above url to get custom fields.so i could olny able to use that schema name alone.

this API returns both logical and schema name are same.

"LogicalName": "new_caseassociate",
"IsValidForForm": true,
"IsRequiredForForm": false,
"IsValidForGrid": true,
"SchemaName": "new_caseassociate",

"LogicalName": "new_lookup_account",
"IsValidForForm": true,
"IsRequiredForForm": false,
"IsValidForGrid": true,
"SchemaName": "new_lookup_account",

*This post is locked for comments

I have the same question (0)

All responses (6)

Answers (0)

Suggested answer

Kalpavruksh D365 CoE 2,545 on at

Like (1)

Report
Hi,

We had this same issue for the custom lookup field.

One of the value from the below list will work for a custom lookup field.

ReferencedEntityNavigationPropertyName

ReferencingEntityNavigationPropertyName

SchemaName

LogicalName

Please download Metadata browser and install in your environment. It is an official solution from the Microsoft.

https://docs.microsoft.com/en-us/dynamics365/customer-engagement/developer/browse-your-metadata

Try to replace the value before @odata.bind.

1 people found this reply helpful.

Was this reply helpful? Yes No
kiruthigarani 34 on at

Like (0)

Report

I have downloaded odata metadata from developer resources, NO LUCK!!
We are using proper web api to retrieve custom fields, that should return all the details of the field don't know the reason for this issue.

kindly help us to achieve this by web api without any tools

Was this reply helpful? Yes No
Suggested answer

kiruthigarani 34 on at

Like (0)

Report

we have achieved this by appending _Task with the schema name ie; new_lookup_account_Task@odata.bind

Was this reply helpful? Yes No
Suggested answer

Vipin J 1,603 on at

Like (0)

Report

Its a schema naming convention problem.

I resolve this using OData naming convention

Refer here for detail: https://vjcity.blogspot.com/2020/05/an-undeclared-property-ccsquoteid-which.html

Was this reply helpful? Yes No
Fedorov 40 on at

Like (0)

Report

Thank God for this thread. I had the same problem, must be something with "Task" being an acitivty-entity or something.

My field ("new_approvinguser") was having the same problems.

The suggestion in one of the answers by adding "_Task" to the odata-property helped, hence:

DOESNT WORK: "new_approvinguser@odata.bind" : "/systemusers(060814F1-48C8-EB11-A999-00505698BCE2)"

WORKS: "new_approvinguser_Task@odata.bind" : "/systemusers(060814F1-48C8-EB11-A999-00505698BCE2)"

Was this reply helpful? Yes No
Lucas H 283 on at

Like (6)

Report

FYI for anyone else trying to solve this:

Adding "_Task" did not work for me.

My solution was to use the **SCHEMA NAME** and NOT the logical name.

I.e, my custom field was "new_contact". Using "new_contact@odata.bind" did not work, but using "new_Contact@odata.bind" did.

Hope this helps someone!

2 people found this reply helpful.

Was this reply helpful? Yes No