Assess
Review your forms, current validation logic, and channels to identify the tables and rules to move into configuration.
Configure form validation rules without code, and apply them consistently across Model-Driven Apps and Power Pages.

Conditional form logic is among the most frequently requested and frequently changed parts of any Dataverse application. Each new rule, such as hiding a field or making another mandatory, usually means custom script, a test cycle, and a deployment. Per-form scripts multiply, rules that depend on related records fall outside standard business rules, and internal apps and external portals drift apart as each carries its own copy of the logic.
LevelShift’s Validation Component turns form validation into configuration. Administrators define rules as simple records, and one reusable engine applies them to any enrolled table across Model-Driven Apps and Power Pages. Rules are authored once, enforced everywhere, and updated without a release cycle.
Define rules by choosing a table, a column, a condition, and an action. Ten conditions, three actions, and two comparison modes cover most validation scenarios.
Faster Changes:
Create or update validation rules through configuration, without requiring a build, test, and deployment cycle.
Evaluate fields on related records through lookups, extending validation beyond what standard business rules can do.
Consistent Experience:
Apply comprehensive validation across related records, supporting consistent rule enforcement across applications using the same rule engine.
Hide, Lock, and Required actions reverse automatically when a condition no longer applies, so fields never stay stuck in a previous state.
Reliable User Experience:
Ensure fields automatically return to the appropriate state when conditions change.
Apply a single rule to multiple target fields at once, replacing sets of near-identical rules.
Lower Maintenance:
Reduce duplicated configurations and simplify ongoing rule management.
Column metadata is published to rule pickers automatically, removing the typing errors behind most "rule does nothing" defects.
Fewer Defects:
Eliminate manual column entry errors that can cause rules to fail.
The configuration form shows only the inputs each rule needs, preventing incomplete or contradictory rules.
Business Ownership:
Enable administrators to configure validation rules confidently, with less dependence on developers.
Every rule is maintained as a Dataverse record, providing a central place to manage rule definitions and their changes.
Built-in Auditability:
Maintain visibility into who changed a rule and when, subject to Dataverse auditing configuration.
Register the tables you want governed. The component reads their column metadata and makes those columns available for rule authoring.
Administrators create rules as records: if this field meets this condition, then hide, lock, or require these fields. No developer involvement is needed.
When a user opens a form, the engine loads that table's rules and applies them instantly, on both the internal Model-Driven App and the external Power Pages site.
Register the tables you want governed. The component reads their column metadata and makes those columns available for rule authoring.
Administrators create rules as records: if this field meets this condition, then hide, lock, or require these fields. No developer involvement is needed.
When a user opens a form, the engine loads that table's rules and applies them instantly, on both the internal Model-Driven App and the external Power Pages site.
Review your forms, current validation logic, and channels to identify the tables and rules to move into configuration.
Import the solution into your environment and connect it to your tables and forms.
Register target tables, publish their columns, and set up initial rules with your administrators.
Configure secure portal access so external forms enforce the same rules as your internal app.
Test rule behavior end to end, train administrators on rule authoring, and provide ongoing support.
Note: Adding more tables later repeats only the enrollment steps. The engine itself is never copied or rewritten.