Business rule

A business rule in Dataverse is a no-code mechanism for adding field-level logic to forms. The graphical designer lets makers configure conditions on field values and actions to take when the conditions are met — set a default value, lock a field, change its required status, show an error message, hide a section, suggest a value (recommendation). Business rules can scope to a single form or to the entire table; entity-scoped (table-scoped) rules run both client-side and server-side, enforcing logic even on API writes that bypass the form entirely, which form-scoped rules cannot do.

In practice, business rules cover the majority of "if X then require Y" logic that would otherwise mean writing JavaScript against the form API — hide the shipping-address section unless "Ships to a different address" is checked, require a cancellation reason once status moves to Cancelled, default the currency from the selected account. Because the designer is visual and the resulting logic runs automatically without a script tag to maintain, business rules are usually the first thing a maker reaches for, and they hold up well under solution upgrades in a way that ad hoc JavaScript sometimes doesn't. Their limits are equally deliberate: single-table only (no reading a related record's fields), no external calls, no loops or complex branching beyond simple AND/OR conditions.

Where confusion shows up: business rules are often reached for past their actual limit, and the failure mode is subtle — a maker tries to reference a related table's field, finds the designer won't allow it, and either abandons the requirement or builds an awkward workaround with a rollup or calculated column instead of just switching tools. The right escalation path is: business rule for single-table field logic, Power Automate flow for anything that touches another table or an external system, JavaScript via the Client API for form-level UI behaviour a business rule can't express, and plug-ins for logic that must be enforced server-side regardless of which client wrote the data.