cookies preferences

Validation Component for Power Platform

Configure form validation rules without code, and apply them consistently across Model-Driven Apps and Power Pages.

Validation Component for Power Platform

Change Validation Rules Without Changing Code

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.

Schedule a Call

Key Features

No-Code Rule Configuration

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.

Cross-Table Conditions

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.

Self-Resetting Actions

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.

One Rule, Many Fields

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.

Automated Column Registration

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.

Guided Rule Authoring

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.

Dataverse-Based Rule Records

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.

How does it work?

Stage 1

Enroll Your Tables

Register the tables you want governed. The component reads their column metadata and makes those columns available for rule authoring.

Stage 2

Configure Rules

Administrators create rules as records: if this field meets this condition, then hide, lock, or require these fields. No developer involvement is needed.

Stage 3

Enforce Everywhere

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.

Our Implementation Approach

01
Assess

Review your forms, current validation logic, and channels to identify the tables and rules to move into configuration.

02
Deploy

Import the solution into your environment and connect it to your tables and forms.

03
Enroll and Configure

Register target tables, publish their columns, and set up initial rules with your administrators.

04
Extend to Power Pages

Configure secure portal access so external forms enforce the same rules as your internal app.

05
Validate and Hand Over

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.

Why LevelShift

Microsoft Specialized Low-Code Solutions Partner

AI-powered low-code solutions tailored to your business

100+ low-code digital transformation projects delivered

Reusable Power Apps templates, components, and accelerators

Integration expertise: connect Power Platform with ERP, CRM, legacy systems, and third-party APIs

Enterprise-grade security, compliance, and continuous optimization

FAQs

The Validation Component is a reusable Power Platform accelerator from LevelShift. It replaces hand-written form scripts with configurable rules. Administrators define when fields should be hidden, locked, or made mandatory, and one engine applies those rules across Model-Driven Apps and Power Pages.
Standard business rules are set up per table and cannot evaluate fields on related records. The Validation Component can follow lookups to check values on related records, apply one rule to multiple fields, and use a single shared rule set for both internal apps and external portals.
No. Rules are created as records by selecting a table, a field, a condition, and an action. A guided form shows only the inputs each rule needs, and fields are picked from automatically generated lists, so there are no technical names to type.
Yes. Rules are authored once and enforced on both internal Model-Driven App forms and external Power Pages forms. This keeps validation consistent across channels and prevents the two experiences from drifting apart over time.
Adding a table only requires registering it and publishing its columns. The engine itself is never copied or rewritten, so each new table is a quick configuration step rather than a development project.

Ready to manage form validation without writing code?