web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics CRM (Archived) / Automatic Branching in...
Microsoft Dynamics CRM (Archived)

Automatic Branching in process flow

(0) ShareShare
ReportReport
Posted on by ChrisJC 1,540

This is the latest version of Dynamics 365 Online.

I have a BPF that has a conditional branch but it is only switching the stage when the opportunity record is closed and reopened. I thought it would happen automatically.

The criteria for the condition is set by calculations in business rules which appears to be the issue. It's updating the field value correctly but not switching the next stage.

How have others handled this? Is there some javascript I can use on change of the criteria field that triggers the BPF to check the stages?

Thanks,

Chris

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Rajkumar Rajaraman Profile Picture
    Rajkumar Rajaraman on at

    Using JavaScript You can achieve this:

    mscrmonline.wordpress.com/.../how-to-automatically-next-stage-on-business-process-flow

  • ChrisJC Profile Picture
    ChrisJC 1,540 on at

    Hi Rajkumar,

    Thanks however I don't want to move to the next stage, I just want to show the correct next stage.

    I've just created a test BPF. I have a two-option field that when I switch changes the next stage between "Yes" and "No"

    6507.2.JPG

    When I update this "File Debrief" field via Business Rule it doesn't switch the next stage:

    6507.2.JPG

  • ChrisJC Profile Picture
    ChrisJC 1,540 on at

    Has anyone else seen this? I have replicated it on two CRMs now.

    When I use the next button it doesn't take it to the correct branch so the previously mentioned javascript won't work.

  • Verified answer
    ChrisJC Profile Picture
    ChrisJC 1,540 on at

    Fixed by replacing the field update by business rule with a calculated boolean field. Add this field to the BPF and change the conditional brancing to branch based on it's value.

    Heard back from Microsoft. The reason why the field updated by business rule doesn't work as it could trigger a circular reference so fields updated by BR don't trigger the onChange event which the BPF branching runs from.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans