Hi Alger, This issue is a known behaviour in Business Process Flows with Yes/No (Two Options) fields, especially when:
The default value ("No") is not manually touched by the user.
BPF validation expects user interaction to register the value.
Options: 1. Pre-populate via Workflow or Power Automate Ensure the field value is explicitly set to "No" using:
A real-time workflow or
Power Automate on record creation
This ensures CRM recognizes the field as populated even if it's the default. 2. Use Business Rules Add a Business Rule on the entity:
Condition: Field is empty
Action: Set field to "No"
This triggers when the form is opened and ensures the value is assigned programmatically. 3. Field Requirement Mode Make sure the field is:
Required at the entity level or in the BPF step, not both.
Sometimes conflicting required settings may confuse BPF evaluation.
The BPF checks for user input, not just whether the field has a default. If "No" is default but untouched, it may be seen as "unset".
Was this reply helpful?YesNo
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.
5
Share
Report
All responses (
Answers (
