Microsoft Dynamics CRM (Archived)

Solution - Patch - Update workflow

(0) Share

Report

Posted on by Dc1

220

Hello

I have sandbox and Prod environment.

I work in a patch solution.

In my patch I have a workflow, i modified in the test and that already exist in prod

when I export the patch as a managed solution and import it in prod the modified workflow in test is not modified in prod but the modified date of the workflow is update to the patch import date.

I checked in the xaml file and it's correct.

When i export the workflow as new solution it's ok , the workflow is updated

then i suppose there are limitation to patch : i found somes here :

https://msdn.microsoft.com/en-us/library/mt593040.aspx

Patches support the same operations as solutions, such as additive update, but not removal. You cannot remove components from a solution using a patch. To remove components from a solution perform an upgrade.

but they do not say anything about workflow.

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (1)

Community Member on at

Like (0)

Report

A way to do this is through computer-telephony integration (CTI), where the CRM is connected to the phone system to ensure a seamless sales call workflow. This is what our application at Tenfold does, linking CRMs to phones so that sales reps can optimize their performance and deliver more results. With Tenfold, users can get functions like screen popup caller ID(inbound and outbound), automatic call logging, task creation, email template integration, social profile integration, among others. They support MS Dynamics integration. Anyone interested can get a demo here: www.tenfold.com/.../dynamics

Was this reply helpful? Yes No
Andreas Cieslik 9,267 on at

Like (0)

Report

What happens if you unpublish the workflow in the target system first? Will the patch be successfull?

Was this reply helpful? Yes No
Dc1 220 on at

Like (0)

Report

you mean set the workflow in draft. that change nothing

Was this reply helpful? Yes No
Suggested answer

Andreas Cieslik 9,267 on at

Like (0)

Report

It could be possible that you might need to roll up all patches to a new solution.

Check section "update a solution" in this article:

msdn.microsoft.com/.../mt593040.aspx

With this upgrade this might work as successfully as well.

And yes there are some limitations compared to new solution versions, e.g. removal of elements.

Another reason could be that you have a running or pending system job based on that workflow you want to replace.

Those need to be completed first prior to replacing/removal of the workflow.

Was this reply helpful? Yes No
Verified answer

Nishant Rana 11,325 Microsoft Employee on at

Like (0)

Report

This is what we also realized. I think it in the production the component would have been updated through default solution before the patch was moved.

nishantrana.me/.../limitation-of-solution-patch-in-dynamics-365

Was this reply helpful? Yes No