15
Hi all,
We recently upgraded CRM2016 on-prem to D365, and a set of workflows that were using the SetProcess action are now not switching the active BPF if a BPF was already in use on a record. They are creating a new BPF session (since D365 now supports multiple BPFs), but when opening the record the old one is still the active visible one. Is there any way, or any further action required, to force D365 to switch to the newly created BPF process?
Thanks,
Adam,
The documentation suggests that you can only change the BPF either via the UI or programmatically via code.
Is there any other possibility to change the BPF via a workflow without coding, i.e. something that replaces the deprecated workflow action 'SetProcess'?
I have the same issue. I have a workflow that fires and checks the current BPF and switches it to another one when necessary. The workflow finishes properly, and if I check the ProcessID in a view it does show that it switched, but when I open the Opportunity it still has the old BPF showing, and if I go up to Switch Process it shows the old process as active. If I switch it manually it shows the new BPF. Has anyone found a solution for this? Looks like it has been happening for awhile now. I am in the German datacenter on Version 1612 (8.2.3.114) (DB8.2.2.1310).
I followed the rules from this Microsoft article:
community.dynamics.com/.../change-business-process-flows-using-a-workflow
Hi Adam,
I am experiencing the same problem, and have contacted Microsoft about it.
The support technician claims to have tried this in a fresh environment without experience what we claim, which suggest it to be a bug.
I will update the post when I hear from them again.
Best regards,
Bjørn
#1
André Arnaud de Cal...
291,703
Super User 2024 Season 2
#2
Martin Dráb
230,433
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (
