Configuring Conditional Mandatory Fields in Model-Driven Apps

The scenario requires enforcing data quality by ensuring a specific column is populated only when a certain condition exists, while preventing the record save until that field is completed. The constraint is to achieve this without code or automation, pointing directly to platform-native validation features within Model-Driven Apps.

In Microsoft Dataverse and Power Apps, Business Rules are the tool designed for declarative logic implementation on entity forms. They can execute actions based on conditions but cannot trigger server-side validations (like webhooks) or complex client-side scripts. To enforce mandatory entry, the correct configuration is to use the Set Requirement Level action within a Business Rule. By setting the requirement level to 'Business Required' under a specific condition, the system automatically validates the field upon submission, blocking the save operation if the field is empty. This aligns perfectly with the 'no code/automation' constraint.

Option A, Show a Recommendation, provides guidance but does not prevent saving. Option B, Set Field Visibility, controls whether a user sees the field but does not enforce data entry. Option C, Set a Default Value, pre-fills data but does not ensure user input or block saves if the default is inappropriate or if the user tries to clear it. Therefore, setting the requirement level is the only mechanism that enforces the mandatory nature of the field conditionally.