Define the components of a business rule
Business rules encapsulate logic in a predefined set of steps. The steps run each time data is entered or modified and the data meets certain criteria to trigger the business rule. The business rule will run whatever way that data was added or edited in the table. Additionally, business rules are server-side, meaning that the logic runs on the servers that manage Microsoft Dataverse.
Business rules have the following components:
Condition - All business rules have a condition. It's a trigger and is used to determine if the business rule is run based on the values that are added or edited in a table. A condition always runs as true or false, and you can have more than one condition in a business rule.
Action - An action is some logic, like setting a column to a certain value, that runs on either the true or false branch of a condition.
Scope - Business rules can have a scope. The following table outlines the available scope options for a business rule.
Tip
A business rule that is used by a canvas app always has the scope set to Table.
| Scope of a business rule | Applies to |
|---|---|
| Table | Model-driven forms and server |
| All forms | Model-driven forms |
| Specific form (Account form, for example) | Just that model-driven form |
Need help? See our troubleshooting guide or provide specific feedback by reporting an issue.