plugin is triggered by workflowaction - how to handle exception in plugin

(0) Share

Report

Posted on by Axi Bachlechner

Hi Community!

I have a complicated situation.

On a form on entity A in CRM 2016 a workflowAction is triggered by clicking on a ribbon-button (via javascript)

In this workflowAction an entity B (totally different type) is updated. On this entity a plugin is registered (only on update). This plugin itself calls a webservice. If webservice-call fails the first workflowaction has to handle this but shouldn't throw an error.

If i throw an InvalidPluginExecutionException in plugin for entity B if webservicecall fails I get "There is no active transaction....."

I also need the failed message the webservice returns, to show what happened, to the user.

How can I handle this?

thx in advance

©a-x-i

I have the same question (0)

All responses (3)

Answers (0)

PabloCRP 1,088 on at

Like (0)

Report
RE: plugin is triggered by workflowaction - how to handle exception in plugin

Hi,

base on how it's build your solution, I wouldn't trow an exception in the plugin, unless a core functionality failed, but for know what happed with the external webservice I'd log in entity B the Response, could be in one memo field and then with the javascript validate the status of the response and like if the response has a status different from 200 then show the body of the response. here and example of what the plugin would log.

{ "statuscode":200, //400,401,etc. "message":"All done!"//Your data it's wrong, no authorized, etc. }

regards.

Was this reply helpful? Yes No
Axi Bachlechner 76 on at

Like (0)

Report

RE: plugin is triggered by workflowaction - how to handle exception in plugin

thank you for your reponse.

The problem is, that I don't want to save entity B if the webserviceCall wasn't successful. So an exception is the only way to trigger a rollback.

a-x-i

Was this reply helpful? Yes No
nyiicco 10 on at

Like (0)

Report

RE: plugin is triggered by workflowaction - how to handle exception in plugin

The web service call executes first before you update entity B. Before you execute the update, you can check first the response code of the web service, if the code is not "200" means there is an error encountered. So instead of proceeding with the update, save the web service response to other entity which the user can check.

Was this reply helpful? Yes No

Join the conversation

Community site session details

plugin is triggered by workflowaction - how to handle exception in plugin

Helpful resources

News and Announcements

Quick Links

Responsible AI policies

Abhilash Warrier – Community Spotlight

Congratulations to the September Top 10 Community Leaders!

Leaderboard > Customer experience | Sales, Customer Insights, CRM

Featured topics

Product updates

Community site session details

plugin is triggered by workflowaction - how to handle exception in plugin

Helpful resources

News and Announcements

Quick Links

Responsible AI policies

Abhilash Warrier – Community Spotlight

Congratulations to the September Top 10 Community Leaders!

Subscribe to this forum!

Select categories

Leaderboard > Customer experience | Sales, Customer Insights, CRM

Featured topics

Product updates