Answered

Ambiguous binding is present. Resolve by sending lookup_type property.

(0) Share

Report

Posted on by Community Power Pla...

I am getting this error when attempting to "Create a new record" within Dynamics 365 on a "Forms" submission.

I have screenshots available below.

{
 "status": 400,
 "message": "Ambiguous binding is present. Resolve by sending lookup_type property.",
 "source": "dynamicscrmonline-ncus.azconn-ncus.p.azurewebsites.net",
 "debugInfo": "clientRequestId: 93f78905-f66b-4e5c-80a0-ff21a62542f5"
}

Let me know if you need further details, I am quite naive with flow.

All responses (4)

Answers (1)

Community Power Pla... on at

Like (1)

Report

Re: Ambiguous binding is present. Resolve by sending lookup_type property.

Hello,

Thanks again for your time and expertise. I will make necessary adjustments and keep you posted!
Verified answer

abm abm 32,506 Most Valuable Professional on at

Like (1)

Report

Re: Ambiguous binding is present. Resolve by sending lookup_type property.

Hi,

Please follow the below steps how to get contactid. Similar techique you can use to get the customerid as well.
First declare a variable called contactid. Then use the list records using the filtery query to get the contact. Assign the contact id to variable. Finally map contactid to Create new record.

If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up.

Thanks
Community Power Pla... on at

Like (1)

Report

Re: Ambiguous binding is present. Resolve by sending lookup_type property.

Thanks for your reply.

I'm not sure where to "list records by Filter query." Is this an option as shown below?
abm abm 32,506 Most Valuable Professional on at

Like (0)

Report

Re: Ambiguous binding is present. Resolve by sending lookup_type property.

Hi @Anonymous

Looks like Case entity primarycontactid and _customerid_value both are expecting a GUID which is a lookup value. You need to find the GUID by using List records by Filter Query. The map the id to Create a new record.

Please see similar post
https://powerusers.microsoft.com/t5/Building-Flows/getting-error-quot-Ambiguous-binding-is-present-Resolve-by/td-p/12970

If you need any futher help please let me know.

If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up.

Thanks