You’re offline. This is a read only version of the page.
129
Hello everyone,
first of all, we are using an 8.2 on premise version.
I am using the OOB action to set a business process for an opportunity. The action is triggered without a problem BUT the action doesn't change the process any more.
In the changelog I can see that the process is being "changed" from the old process to the old process, instead of the new one.
I tried using the "Set Business Process" Action from the Dynamics Workflow tools as well. Even stranger result. The process gets changed (according to the changelog) BUT on the UI I still see the old business process being displayed. (Yes, I pressed F5 multiple times). Never had this issue before 8.2.
Anyone else who had this issue before and found a solution? (I don't want to write a JScript to solve it, wanna get the actions back to work).
I really appreaciate any help and input I can get. If further information is necessary of if my description of this strange problem is unclear, please let me know.
Best regards,
Daniel
*This post is locked for comments
Hi Daniel,
try to set the workflow as real time workflow and set it to run under user instead of workflow owner.
but in the end you will need the Js to help other user (not the owner of the record) to switch the process if the user opened the record before.
[View:https://msdn.microsoft.com/en-us/library/dn817878.aspx#BKMK_setActiveStage]
Hi,
thanks for your quick reply. So I guess my problem is connected to the visibility of the BPF.
The workflow which changes the process for my tests is run by the admin user and the current user is the admin user, so I hoped it would change the WF for this user. However, the process doesn't change in the frontend. Maybe the action is just not working at the moment, still putting values in the old fields.
Still searching for a workaround without JScript. (OR I need an almost ready template)
Best regards
Daniel
Hi,
With Dynamics 365, the bpf is a little bit different compare to previous one, so read about it via below post.
Dynamics 365 bpf vs Previous CRM BPF
[View:http://alexmscrm.blogspot.my/2017/10/dynamics-365-business-process-flow-and.html:750:50]
What is Concurrent bpf
[View:https://blogs.msdn.microsoft.com/crm/2017/03/28/concurrent-business-process-flows-in-dynamics-365/:750:50]
ProcessId, StageId, and TraversedPath fields are depreacated
[View:https://blogs.msdn.microsoft.com/crm/2017/07/30/how-to-determine-which-business-process-flow-bpf-instance-is-shown-when-a-record-is-opened-2/:750:50]
the possibilities would be, the workflow you are trigger is not running on your context.
#1
Mohamed Amine Mahmoudi
83
Super User 2025 Season 1
#2
Community Member
54
#3
Victor Onyebuchi
6
Share
Report
All responses (
Answers (
