Adding Business Rule Scope to Model-Driven App Quick Create Form

Correct Answer: D

Microsoft Dataverse Business rules contain logic that users want to apply to the data.

The rules consist of three parts: conditions, actions, and scope.

A business rule is triggered when data meets the condition defined by the rule.

After the rule is triggered, it performs defined actions within the scope.

The scope of the rule is limited to the Entity, All Forms, and Individual Forms.

The canvas apps always have an Entity scope for their business rules.

The model-driven apps have the Entity and two other scopes.

The Entity has a global scope: the rule runs whenever a record is created or updated by any Power Platform products or API calls.

The All Forms scope makes sure that a business rule runs on all forms of your app, including Quick Create forms.

If you need your rule to run only on one form, you need to be sure that it is the Main type.

Then you can choose the form name (like Input form) from the Scope dropdown in the Rule Designer and use the action that is limited to the forms.

All other options are incorrect because we need a rule to run when a user saves a record.

The only rule with the Entity scope can do this.

For more information about Dataverse business rule scope, please visit the below URLs:

When adding a business rule to a model-driven app, you need to consider the scope of the rule carefully. The scope determines which parts of the app the rule will apply to. In this case, the business rule should run after a user fills the Quick Create form and saves the record.

A Quick Create form is a simplified form that allows users to quickly create new records. It usually contains only a few fields and is often used in scenarios where users need to enter data quickly without navigating to a full form.

Considering the above, the answer to this question would be option A: Quick Create form. This is because we want the business rule to apply only to the Quick Create form and not to other forms or screens in the app.

If we choose option B: Main form, the rule would apply to the main form of the entity, not the Quick Create form. Option C: All screens, would apply the rule to all screens in the app, which is not necessary in this case. Finally, option D: Entity, would apply the rule to all forms and screens for the entity, which is broader than necessary.

In summary, when adding a business rule to a Quick Create form in a model-driven app, the scope should be set to the Quick Create form.