Featured Post

Dynamics 365 - Business Process Flow and Things to take note before you upgrade into Dynamics 365.

In 2 months ago, my company decided to upgrade the Dynamics CRM 2016 into Dynamics 365 and there is something different about Dynamics 365 B...

Friday, November 10, 2017

Dynamics 365 - Thinking to trigger a workflow when switching a Business Process Flow? You better think twice :)

Before Dynamics 365, we can easily create a workflow and trigger it when user is switching a process by follow the below setting.


But With Dynamics 365, the behavior is very different from previous version.

Before we start the demo, i suggest you to read this article so that you have better understanding about the new BPF structure in Dynamics 365.

DEMO 

1. I will create an opportunity record.



2. Let's switch into another process




  •     The Modified on get updated.





  •     From the Audit History, Process ID, Stage ID and Traversed Path are working perfectly.



3. After few minutes, Let's switch back to first BPF.


 

  •     From the picture below, do you notice anything?




  •     Yes, no fields get updated anymore.   
  •     Even the BPF record stays where you created them.



DEMO 2

1. Now, i created 2 workflows and applied them into BPF.
   


2. Let's create an opportunity record.

  •     the description is updated.


2. Let's switch the process

  •   The description get updated too.



3. Let's switch back to first process
  • the description no longer get updated.



So, from the 2 demos above, do you realize anything?

  • once process is applied,
           - it will not trigger the workflow anymore.
           - it will not update the process id ,stage id and traversed path on entities anymore.
Conclusion
  • You should stop using Process id, Stage id and Traversed path on entities  because these fields will be deprecated soon.
  • You can refer the MSDN Article here.
I hope this will get you alert about this behavior and Happy CRM-ing

No comments:

Post a Comment