What Business Rules Do
Business rules are a no-code way to apply logic directly on a Dataverse table, letting makers set field values, show or hide fields, mark fields required, show error or warning messages, and enable or disable fields based on conditions — without writing JavaScript. Each rule is built from an if/then condition tree in a visual designer, and a single table can have multiple rules that all execute when a record is created or updated.
Cricket analogy: A business rule is like an umpire's automatic no-ball call triggered the instant a bowler oversteps the crease, applying a consistent rule without a human needing to manually check every delivery.
Scope: Entity vs. Form
Every business rule has a scope: Entity scope runs the logic everywhere the table is used, including server-side on the Dataverse Web API and mobile offline, while Form scope only runs client-side on a specific form and cannot enforce true server-side validation. Entity-scoped rules are preferred for real business validation you want enforced everywhere, while Form-scoped rules are useful for interface behavior specific to a single form layout, like hiding a field only on a Quick Create form.
Cricket analogy: Entity scope is like an ICC rule that applies in every match worldwide, while Form scope is like a domestic league's local house rule that only applies on that particular ground.
Conditions and Actions
A business rule's condition tree evaluates one or more field comparisons combined with AND/OR logic, and each branch can trigger actions: Set Field Value (including setting it to another field's value), Set Business Required, Set Visibility, Set Default Value, Lock or Unlock Field, and Show Error/Recommendation Message. For example, on an Opportunity table, a rule might check if Estimated Close Date is more than 90 days out and, if true, set Priority to 'Low' and unlock the Discount field.
Cricket analogy: A DRS (Decision Review System) condition tree checks ball-tracking data against multiple criteria (pitching in line, hitting the stumps) before triggering the 'Out' or 'Not Out' action, just like a business rule's branching logic.
IF
Estimated Close Date Greater Than {Today + 90 days}
THEN
Set Field Value: Priority = "Low"
Unlock Field: Discount Percentage
ELSE
Set Field Value: Priority = "High"
Lock Field: Discount Percentage
Show Error Message on Discount Percentage:
"Discounts require manager review for near-term deals."Business rules execute in a defined order shown in the rule list; if two rules could conflict (one sets a field required, another hides it), reorder them via the 'Order' column so the intended outcome always wins.
Form-scoped business rules only run in the browser and do not protect data created through the Web API, Power Automate, or data import — use Entity scope, or a real-time workflow/plugin, whenever the validation must be enforced everywhere.
- Business rules apply no-code if/then logic to a table without writing JavaScript.
- Entity scope enforces logic everywhere the table is used, including the Web API; Form scope is client-side only on one form.
- Available actions include Set Field Value, Set Business Required, Set Visibility, Lock/Unlock Field, and Show Error/Recommendation Message.
- Condition trees combine multiple field comparisons using AND/OR logic before firing an action.
- Multiple business rules on the same table execute in a defined, reorderable sequence.
- Form-scoped rules cannot guarantee validation for records created outside that specific form.
- Business rules are best for simple, declarative validation; complex logic usually needs Power Automate or plugins instead.
Practice what you learned
1. What is the primary advantage of a business rule over writing custom JavaScript?
2. Which scope should you use if a validation must be enforced even when records are created through the Web API?
3. Which of the following is NOT a valid business rule action?
4. Why might a Form-scoped business rule fail to prevent invalid data during a bulk data import?
5. When two business rules on the same table could both affect the same field, what determines which one wins?
Was this page helpful?
You May Also Like
Dataverse Tables and Relationships
Learn how Microsoft Dataverse organizes data into tables, columns, and relationships that power Model-Driven and Canvas apps.
Forms, Views, and Charts
Understand how Model-Driven Apps present Dataverse data through configurable forms, views, and charts.
Security Roles in Dataverse
Understand how Dataverse security roles, privileges, and access levels control who can see and do what with your data.
Related Reading
Related Study Notes in Microsoft Technologies
Browse all study notesWindows 10 / UWP Development Study Notes
.NET · 30 topics
Microsoft TechnologiesWindows Batch Scripting Study Notes
Batch · 30 topics
Microsoft TechnologiesMFC (Microsoft Foundation Classes) Study Notes
C++ · 30 topics
Microsoft TechnologiesSilverlight Study Notes
.NET · 30 topics
Microsoft TechnologiesXAML Study Notes
.NET · 30 topics
Microsoft TechnologiesWPF (Windows Presentation Foundation) Study Notes
.NET · 30 topics