Add a Business Rule to a Model-Driven App in Power Platform | PL-400 Exam | Microsoft

Add a Business Rule to a Model-Driven App

Question

You create a model-driven app.

The app has a Quick Create Form.

You need to add a business rule that would run after a user fills the form and saves the record.

What should be the scope of this rule?

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D.

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's Quick Create Form, the scope of the rule depends on the intended functionality and the specific needs of the app.

Option A: Quick Create Form scope would apply the business rule only when the record is created using the Quick Create Form. This means that the rule will only run when the user creates a new record using the Quick Create Form, and not when they use the main form or any other screen.

Option B: Main Form scope would apply the business rule only when the record is edited using the Main Form. This means that the rule will only run when the user edits an existing record using the Main Form and not when they use the Quick Create Form or any other screen.

Option C: All screens scope would apply the business rule to all screens, including the Quick Create Form, Main Form, and any other screen. This means that the rule will run whenever the user creates a new record, edits an existing record, or uses any other screen in the app.

Option D: Entity scope would apply the business rule to all screens and forms associated with the entity. This means that the rule will run whenever the user creates a new record, edits an existing record, or uses any other screen or form associated with the entity.

Therefore, the correct answer would depend on the specific requirements of the app. If the business rule should only apply to records created using the Quick Create Form, then the scope should be set to "Quick Create Form" (Option A). If the rule should apply to all screens, then the scope should be set to "All screens" (Option C). If the rule should apply to all screens and forms associated with the entity, then the scope should be set to "Entity" (Option D).