Custom action with a complex input parameter (entityreference)

(0) Share

Report

Posted on by Community Member

I create a global (unbound) action in Dynamics 365 (new_newAction) that accepts an input parameter ( of name Target ) with type (EntityReference) and activate it.

I checked that my action is available throw WebAPI

I want to call it in a JavaScript method, but for testing I wanted to call it from a REST Client ( example Postman, Insomnia SoapUI).

To do that I did the following :

- I use method POST with a json payload

- I put my credential ( other calls to the WebAPI endpoint work)

- I put the Url : server/organization/api/data/v8.2/tgz_newAction

- I put necessary headers :

Accept: application/json

OData-MaxVersion: 4.0

OData-Version: 4.0

Content-Type: application/json; charset=utf-8

- I put the payload but it’s not correct

Example :

{

"inputTarget" :

{

"@odata.type": "Microsoft.Dynamics.CRM.crmbaseentity",

"@odata.id": "78713858-5e81-df11-afdb-00155dba380a",

"@odata.LogicalName": "new_entity",

"@odata.Name": "new_entity"

}

But that it’s not working. Do you have any idea ?

*This post is locked for comments

I have the same question (0)

All responses (12)

Answers (1)

Suggested answer

a33ik 84,331 Most Valuable Professional on at

Like (1)

Report

Hello Fouad,

Define particular entity type for your input.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

the problem is that i want that my plugin be used for différents entities. (

Was this reply helpful? Yes No
Suggested answer

a33ik 84,331 Most Valuable Professional on at

Like (1)

Report

Then the easiest solution for you is to use string field and pass serialized version of entity reference inside.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

why we have the possibility to define a entityreference and not to use it.

Was this reply helpful? Yes No
Suggested answer

a33ik 84,331 Most Valuable Professional on at

Like (1)

Report

I believe it would work with SOAP endpoint (when Actions were introduced). Looks like it's platform limitation of WebApi endpoint.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

thank you for your speed answers.

Was this reply helpful? Yes No
Verified answer

Community Member on at

Like (2)

Report

I make it worked when i use the following payload :

{

"inputTarget" :

{

"@odata.type": "Microsoft.Dynamics.CRM.new_NewEntity",

"new_NewEntity.id": "78713858-5e81-df11-afdb-00155dba380a",

// no need to put name and logical name.

}

}

Was this reply helpful? Yes No
Suggested answer

Daryl LaBar 500 Most Valuable Professional on at

Like (3)

Report
Your solution has a typo, "new_NewEntity.id" should not have the period before "id" ("new_newentityid") and I believe it should be lowercase as well.

{ "inputTarget" : { "@odata.type": "Microsoft.Dynamics.CRM.new_NewEntity", "new_newentityid": "78713858-5e81-df11-afdb-00155dba380a", // no need to put name and logical name. } }

Was this reply helpful? Yes No
Suggested answer

Arun Vinoth 11,615 Moderator on at

Like (1)

Report
Yes Daryl is right. This below line

"new_newentityid": "78713858-5e81-df11-afdb-00155dba380a",

should has either new_newentityid or "new_newentityid"

Double quote (") is ok. No need of identifier (@) or dot (.)

"new_newentityid": "78713858-5e81-df11-afdb-00155dba380a",

or

new_newentityid: "78713858-5e81-df11-afdb-00155dba380a",

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hello everyone,

Doing pretty much the same - calling Action with JS:

let parameters = {};

parameters.myParameter = {

"inputTarget" :

{

"@odata.type": "Microsoft.Dynamics.CRM.new_myEntity",

"new_myEntityid": parent.Xrm.Page.data.entity.getId().replace(/[{}]/, ''),

}

}

parameters.Target = {

entityType: "new_myEntity",

id: entityId,

};

But getting an error: Input field type 'JObject' does not match expected type 'EntityReference' for field 'myParameter'

Any suggestions on what am I doing wrong?

Thanks in advance.

Was this reply helpful? Yes No