Microsoft Dynamics CRM (Archived)

Global Actions not work, return 204

(0) Share

Report

Posted on by Community Member

Hi Experts,

In my current project ,I set a workflow which type is an Global Action , and there are two steps in it .

Step 1, Run custom workflow(registered with sandbox mode) and return a output parameter.

Setp 2, assign a value for the Action argument.

This works fine over a period of time!

but something strange happens. when i export my Dev environment solution to my Test solution ,i call this action using javascript , it returns http status code 204.

and i couldn't found any reason about this.

could you help me with this ?

Thanks a lot!

2146.a.png 4212.b.png

*This post is locked for comments

I have the same question (0)

All responses (13)

Answers (0)

AJAnsari 5,754 on at

Like (1)

Report

Hi,

You've asked your question in the wrong community. This community is for users of Microsoft Dynamics 365 Business Edition / Dynamics 365 for Financials.

You'll have better luck with your inquiry in the Dynamics CRM or Dynamics 365 Enterprise Edition Community.

Was this reply helpful? Yes No
Community Member on at

Like (1)

Report

Thanks ,i will delete my question later

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Experts,

In my current project ,I set a workflow which type is a Global Action , and there are two steps in it .

Step 1, Run custom workflow(registered with sandbox mode) and return an output parameter.

Setp 2, assign a value for the Action argument.

This works fine over a period of time!

but something strange happens. when i export my Dev environment solution to my Test solution ,i call this action using javascript , it returns http status code 204.

and i couldn't found any reason about this.

could you help me with this ?

Thanks a lot!

Was this reply helpful? Yes No
ashok teja 290 on at

Like (0)

Report

Hello,

Have a look at the following link and verify your script once.

osmosee.wordpress.com/.../dynamics-365-trigger-action-using-js

Thanks

Ashok J

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Thanks Ashok, but i have simulated the request using Fiddler,it also return 204,i think the javascript is ok ,and i have no ideas now !

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

i have simulated the request with Fiddler ,it also return 204 !

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

I have the same problem :(

Did you find a solution?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

we call the Global Action using    the soap envelope captured by the SOAPLogger instead of normal Request.

the request is like the following codes.

var request = [];

     request.push("<s:Envelope xmlns:s=\"schemas.xmlsoap.org/.../envelope\">");
     request.push("<s:Body>");
     request.push("<Execute xmlns=\"schemas.microsoft.com/.../Services\"");
     request.push(" xmlns:i=\"www.w3.org/.../XMLSchema-instance\">");
     request.push("<request i:type=\"b:AssignRequest\"");
     request.push(" xmlns:a=\"schemas.microsoft.com/.../Contracts\"");
     request.push(" xmlns:b=\"schemas.microsoft.com/.../Contracts\">");
     request.push("<a:Parameters xmlns:c=\"schemas.datacontract.org/.../System.Collections.Generic\">");
     request.push("<a:KeyValuePairOfstringanyType>");
     request.push("<c:key>Target</c:key>");
     request.push("<c:value i:type=\"a:EntityReference\">");
     request.push("<a:Id>" + this._xmlEncode(Target) + "</a:Id>");
     request.push("<a:LogicalName>" + this._xmlEncode(Type) + "</a:LogicalName>");
     request.push("<a:Name i:nil=\"true\" />");
     request.push("</c:value>");
     request.push("</a:KeyValuePairOfstringanyType>");
     request.push("<a:KeyValuePairOfstringanyType>");
     request.push("<c:key>Assignee</c:key>");
     request.push("<c:value i:type=\"a:EntityReference\">");
     request.push("<a:Id>" + this._xmlEncode(Assignee) + "</a:Id>");
     request.push("<a:LogicalName>systemuser</a:LogicalName>");
     request.push("<a:Name i:nil=\"true\" />");
     request.push("</c:value>");
     request.push("</a:KeyValuePairOfstringanyType>");
     request.push("</a:Parameters>");
     request.push("<a:RequestId i:nil=\"true\" />");
     request.push("<a:RequestName>Assign</a:RequestName>");
     request.push("</request>");
     request.push("</Execute>");
     request.push("</s:Body>");
     request.push("</s:Envelope>");

var req = new XMLHttpRequest();
req.open("POST", SDK.SOAPSamples._getClientUrl(), true)
// Responses will return XML. It isn't possible to return JSON.
req.setRequestHeader("Accept", "application/xml, text/xml, */*");
req.setRequestHeader("Content-Type", "text/xml; charset=utf-8");
req.setRequestHeader("SOAPAction", "schemas.microsoft.com/.../Execute");
req.onreadystatechange = function () { SDK.SOAPSamples.assignResponse(req, successCallback, errorCallback); };
req.send(request.join(""));

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Any one find other solutions ?

Was this reply helpful? Yes No
Suggested answer

Simon Tooley 60 on at

Like (0)

Report
Hi Tencent,

We have been experiencing the same issue and have found a couple of ways of fixing the issue:

Restart the CRM application pool - obviously not a brilliant solution for a live system

Correct the incorrect XAML of the workflow action generated by the CRM UI (explained below)

It appears that there is a bug in the CRM Workflow UI when generating steps for global CRM actions. Whenever a step is added and the action is saved the XAML of the action is generated with a Target entity parameter of null, if you go back and change the name of the action and save it and then revert it back the XAML will no longer contain the Target parameter which is correct. This is the resolution whenever an action is created/updated:

Generate the action and save it

Change the name of the action and save it

Revert the name back to the original and save it

The XAML will now no longer contain the Target parameter and will now import without any issue

The following SQL query will list any workflow actions that have the Target parameter referenced:

select workflowid,name, xaml, statecode,createdon, primaryentity from workflowbase

where Xaml like '%<x:Property Name="Target"%'

and statecode=1 and category=3 and type=1 and primaryentity=0

order by name

I've tried this out and once this solution is imported over the top of over solutions the global action continues to work. Note, if the action is already returning 204 before the solution is imported then the CRM applicaiton pool will need to be restarted.

Hope this helps.

Regards,
Simon Tooley
Time4Advice

Was this reply helpful? Yes No