Tables, columns, relationships, forms, views, and searching describe the structure of your data and how it's displayed and found. A business rule is the first bit of actual behavior: simple if-this-then-that logic that reacts to what's happening on a form, configured entirely through point-and-click settings — no code.
- A business rule is if-this-then-that logic that reacts instantly on a form
- No code required — built through a point-and-click designer
- Every rule has a scope: one specific form, or the entire table
- Different tool from a Business Process Flow — covered two chapters ahead
Like a dashboard warning light, not a road trip
Picture the warning light on a car's dashboard. Fuel drops below a point, the light switches on immediately — no multi-step process, just an instant reaction to one condition being true right now. A business rule behaves the same way: "if this field equals this value, then do that," checked continuously while someone is on the form.
That's different from planning a whole road trip with multiple stops in order. Dynamics 365 CE has a separate tool for that — a Business Process Flow, covered a couple of chapters ahead — which guides a user through several stages over time. A business rule is the fast, reactive warning light, not the itinerary.
| Condition (if) | Action (then) |
|---|---|
| Status = Cancelled | Require a Cancellation Reason |
| Country = USA | Show the State field |
| Priority = High | Set Follow-Up Date to a default value |
Where a business rule applies: its scope
Every business rule has a scope — how far its reach extends. Two common choices for a beginner:
- Form scope — the rule only runs on one particular form layout. Useful when the logic only makes sense for one audience, like a rule that only matters on the form the service team uses.
- Table (entity) scope — the rule runs everywhere that table's data is edited, on every form built on it. Right when the logic should always apply, no matter which form is open.
Too broad a scope can surprise people on a form the rule wasn't designed for. Too narrow, and the rule silently doesn't apply somewhere it should. The useful question: "should this logic apply no matter which form is open, or only on this one?"