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

Notifications

Announcements

Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Apps / Business Process Flow ...
Power Apps
Unanswered

Business Process Flow - Not recognising default value as completing a field

(0) ShareShare
ReportReport
Posted on by

I have a Business Process Flow (BPF) that is set to assist staff with completing a form. For the most part it works fine, except when offered a Yes/No question where the default option is selected (i.e. the default is No and the answer is No).

  1. This happens both prior to and after creating the record.
  2. Setting the value to Yes and then back to No does not work (even before/after saving). Once the value is No/Default it will not progress the BPF.
  3. The Yes/No field is set as a toggle in a Model Driven App


Screenshots display behaviour exhibited. Is this an issue with using a toggle, an issue with BPF when using a default option or something else?

Post create, default value showing field not completed.Post create, default value showing field not completed.

Prior to create, non-default value showing field completed.Prior to create, non-default value showing field completed.

Prior to create, default value showing field not completed.Prior to create, default value showing field not completed.

Categories:
I have the same question (0)
  • EddieE Profile Picture
    4,641 Moderator on at

    @Anonymous 

    Whilst you may find help for your Model-Driven app question in this forum, I tend to find that better help for these MDA questions can be found in the DataVerse Forum, here

    https://powerusers.microsoft.com/t5/Microsoft-Dataverse/bd-p/CDS_Apps

  • Doxelnaut Profile Picture
    on at

    I am not sure if you have found a solution to this yet or not, but we are running into the same issue. I have found an older write up (linked below), that describes the issue as BPF not handling the No path of a Yes/No field properly. As explained in this article, the issue can also occur with a Choice field if the label is "No" and the value is 0.

    The proposed workaround is to use a Choice with a label and value other than No and 0. You can add logic to set this choice behind the scenes if you want to tie it to your Yes/No field in order to keep your toggle control on the main form. You would then use the Choice field instead of the Yes/No field in your BPF logic.

    Stage-gating a Business Process Flow using two-options attribute type in Dynamics 365 Customer Engagement 

  • lmd-be Profile Picture
    8 on at

    2024 and this problem still exists.... 

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

Forum hierarchy changes are complete!

In our never-ending quest to improve we are simplifying the forum hierarchy…

Ajay Kumar Gannamaneni – Community Spotlight

We are honored to recognize Ajay Kumar Gannamaneni as our Community Spotlight for December…

Leaderboard > Power Apps

#1
WarrenBelz Profile Picture

WarrenBelz 739 Most Valuable Professional

#2
Michael E. Gernaey Profile Picture

Michael E. Gernaey 343 Super User 2025 Season 2

#3
Power Platform 1919 Profile Picture

Power Platform 1919 268

Last 30 days Overall leaderboard