A farm uses a canvas app to manage schedules for planting fields with crop seeds. The farm uses business intelligence to provide recommendations for…

Business rules in a canvas app are only executed when their scope is set to 'Table'. This configuration ensures the rule runs on the server side against the Dataverse table itself. Consequently, the logic is consistently applied whenever the table's data is created or updated, regardless of the client application being used—be it a canvas app, a model-driven app, or an API call. The other scope options are client-side and exclusively apply to model-driven apps, not canvas apps.

B. All Forms: This scope is client-side and only applies to all forms within a model-driven app. It does not execute for canvas apps.

C. Form specific: This scope is also client-side and is restricted to a single, specific form within a model-driven app, not a canvas app.

1. Microsoft Learn. (2023). Create a business rule for a table. In Power Apps documentation. Retrieved from https://learn.microsoft.com/en-us/power-apps/maker/data-platform/create-business-rule.

Reference Specifics: Under the "Set the scope for the business rule" section

the documentation explicitly states

"If you're creating a business rule for a canvas app

you must set the scope to the table." It further clarifies that setting the scope to a form or "All Forms" will prevent the business rule from running in a canvas app.

2. Microsoft Learn. (2023). Types of business rules. In Power Apps documentation. Retrieved from https://learn.microsoft.com/en-us/power-apps/maker/data-platform/data-platform-business-rules#types-of-business-rules.

Reference Specifics: This section distinguishes between client-side and server-side execution. It notes that rules with a scope of 'Table' (referred to as 'Entity' in older documentation) run on the server

making them applicable to canvas apps

while form-scoped rules run on the client (in model-driven apps).