Entity Scope for Business Rules Used by Canvas Apps

AB-410 By islever Editorial Last updated

Implement business and process logic

Short answer

D Set the business rule scope to Entity so the logic evaluates on the custom table row and applies to the canvas app screen Screen1.

Question

You are creating a business rule to implement new business logic.
You must apply the business logic to a canvas app that has a single screen named Screen1. The business rule is scoped to a custom table, with a single form named Form1.
You need to configure the scope for the business rule.
Which scope should you use?
  1. Form1
  2. Global
  3. All Forms
  4. Entity Correct Answer

Key Takeaways

The question tests which business rule scope reaches a non-form client; the trap is assuming that because the rule is defined with Form1, form or All Forms scope will apply in the canvas app.

A Dataverse business rule must use Entity (table) scope to run against the custom table whenever its record changes, which is the only scope that affects a canvas app such as Screen1. The correct option is D.

Common mistake: Choosing A (Form1) because the rule is authored on that form — form scope only evaluates inside the model-driven form runtime and never fires in a canvas app.

Expert Analysis

What the scope choices mean A business rule in Dataverse can be scoped at three levels: a single form, all forms (now "All Forms" on a table), or the table/entity itself. Form-scoped and All Forms rules are evaluated by the client-side form runtime, so they only fire while a model-driven form is loaded. Entity/Table scope is stored and evaluated against the table record itself, which means it runs whenever the record is created or updated regardless of which client touched it.

Why the canvas app forces option D The scenario states the logic must reach a canvas app with one screen, Screen1, and the rule is defined on a custom table with one form, Form1. A canvas app does not render Dataverse forms at all — it reads and writes table rows through the Dataverse connector — so Form1 (option A) and the All Forms scope (option C) never execute in that surface. A comment in the discussion captures this exactly: only business rules at the entity level can have an effect on canvas apps. Therefore the correct choice is D. Entity (labelled "Table" in the current designer).

The adjacent decision and the flip condition If the same rule had to appear only inside a model-driven app's Form1, you would choose A. Form1 for least-privilege, form-specific behaviour; if it had to apply to every form of that table but still not to canvas apps, you would choose C. All Forms. B. Global is not a Dataverse business rule scope at all — it is a distractor borrowed from other rule engines — and even if it were, global rules in Power Apps are the formula-scoped If/With pattern, not table logic.

Operational consequence of getting it wrong Choosing A or C produces a rule that appears to save successfully but silently never fires in Screen1; the canvas app keeps writing stale values, users see inconsistent data, and debugging is painful because no error surfaces. On AB-410, remember the rule: canvas app + Dataverse table ⇒ entity/table scope.

Exam Strategy

When a question names a canvas app, immediately eliminate any form-based scope, because canvas apps never load Dataverse forms — only entity/table scope evaluates server-side on the record. Then check whether the distractor is a real Dataverse scope at all: terms like Global usually belong to a different rule engine and are safe to discard. Apply this same elimination to questions pairing model-driven forms with canvas surfaces.

Frequently Asked Questions

Why does a canvas app ignore Form1 and All Forms business rule scopes?

Canvas apps do not render Dataverse forms, so form-scoped and All Forms rules, which are evaluated by the form runtime, never execute. Only Entity (table) scope runs against the record itself whenever it is created or updated.

What is the difference between Entity scope and All Forms scope?

All Forms applies the rule across every model-driven form of that table but still requires a form to be open. Entity (Table) scope evaluates on the row itself, so it also covers canvas apps, portals and other non-form clients.

Is Global a valid business rule scope in Dataverse?

No. Dataverse business rules offer form, All Forms and Entity/Table scope only; Global is a distractor and belongs to other Power Platform rule patterns such as canvas app formulas.

More AB-410 FAQ →

Community Votes

D
100%

100% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 1 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 1

  1. ah2006 👍 1 Answered D
    Only Busines Rules on Entity can have effect on Canvas Apps

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

How to Configure Manager and Position Hierarchy in Power Apps?

S-grade

Configure Business Process Flow Branching and Automation

S-grade

Preventing Table Display Name Changes During Promotion

S-grade

Configuring Visual Insights in Model-Driven Apps

S-grade

← Back to AB-410 Study Guide