Interaction guide

Validation data grid documentation

Validation shows when a value is checked and how the result appears. This demo uses info, warnings, and hard errors so the feedback stays easy to scan.

What it means

Validation decides when edit rules run and what feedback users see when a value does not meet the expected rule.

When to use it

Use blocking validation when bad data would break downstream logic or make the workflow impossible to complete safely. Use warning-style validation when users should keep moving but still need to see that a value deserves follow-up.

Implementation notes

Keep rules as close as possible to the business language the user already knows. Validation messages should explain what to fix, not just that something went wrong.

Relevant API

Start with validation.enabled, validation.mode, validation.validateOn, validation.validateDebounceMs, validation.validateOnVisibleChange, validation.validateVisibleOnly, validation.validateVisibleDebounceMs, validation.validateAllToken. Open the live API reference for types and defaults.