Custom Workflow Activity - Input Parameters

(0) Share

Report

Posted on by Zeshan Khan

185

Hello Everyone,

Question is adding or removing input parameters in Custom Workflow Activity is not effected until I unregistered the assembly and registered again. This re registering step forces me to remove all the assembly steps in workflow and if my Workflow has many calls to this assembly this rework reduces productivity.

Can anybody knows is there any way using which I can get rid of this rework and get my new input params without unregister the assembly?

Regards,

Zeshan Khan

SR. CRM Consultant

*This post is locked for comments

I have the same question (0)

All responses (20)

Answers (1)

Suggested answer

a33ik 84,331 Most Valuable Professional on at

Like (1)

Report

After you updated content of assembly try to click "Save" button like it is shown on following image:

Was this reply helpful? Yes No
Suggested answer

Luke Sartain 1,266 on at

Like (0)

Report

I have heard of others who had this problem which they believed could be down to the way CRM caches custom actions. If you're on premise doing an IIS reset apparently resolves the issue but if you're online you may need to wait a number of hours before the cache is reset.

Was this reply helpful? Yes No
Suggested answer

ARIFNIIT 1,391 on at

Like (0)

Report

I think you when you will update assembly with add/Remove parameter it will be reflected in workflow but you need to refresh workflow page.

Was this reply helpful? Yes No
Abdul Wahab 12,119 Moderator on at

Like (0)

Report

Hi Andrew,

I am trying as you suggested but no luck.

Thanks

Best Regards,

AW

Was this reply helpful? Yes No
Verified answer

RaviKashyap 55,410 Moderator on at

Like (0)

Report

Hi Abdul,

As per the MSDN, if you are making significant changes to your custom workflow activity such as adding or removing some actions or changing the input/output parameters then you should upgrade your custom workflow activity by updating the major version of the workflow assembly and then registering it separately. This will add another higher version of your assembly and then you need to update the workflow to use this new version.

Check this:

msdn.microsoft.com/.../gg328011.aspx

Hope this help.

Was this reply helpful? Yes No
Zeshan Khan 185 on at

Like (0)

Report

Not working on refreshing

Was this reply helpful? Yes No
Zeshan Khan 185 on at

Like (0)

Report

Anyone has done it with POC?

Was this reply helpful? Yes No
Suggested answer

RaviKashyap 55,410 Moderator on at

Like (0)

Report

Hi Zeshan,

Did you check the MSDN link I shared above? If you make changes to input/ output parameters, you should release an upgrade of your current assembly by incresing the major version of the assembly.

msdn.microsoft.com/.../gg328011.aspx

When you change the major version, you need to re-register the assmbly. This will ensure that your existing workflow will run on the old version and you can then create new workflows with the new version.

Hope this helps.

Was this reply helpful? Yes No
Zeshan Khan 185 on at

Like (0)

Report

Hi Ravi,

I followed that link. But it is not solving the problem. When I upgraded the Assembly version and went to update workflow assembly in Plugin Registration Tool. It is asking me to remove all the references first. Actually this is the problem.

We are looking for a solution where we can get new input parameters in existing workflows without removing existing references in Worklfows.

Was this reply helpful? Yes No
Suggested answer

RaviKashyap 55,410 Moderator on at

Like (0)

Report

Hi Zeshan,

When ypu release an upgraded version i.e. by increasing the major version, you need to register the assembly again. That way you old workflows will still be referencing ols assembly version and for new worlflow you can use the new version.

You dont need to remove the old references as it will continue to use tge old version.

Basically once you regiater the upgraded assembly again, in worlflow editor, crm will give you an option to choose the version i.e. 1.0 or 2.0 etc

This is the supported/recommended approach. And if Iam not wrong this is used by crm itself for psa, portals field service solutions

Hope this help

Was this reply helpful? Yes No