How to Validate Data?

Custom Data v2 has no separate Validate entire table button. Checks happen when you save records, during import (Preview before import), and through field rules set in the table editor.

When Needed

You need to ensure new rows follow rules (email, required, unique).
You import a file and want errors before rows are written.
Operators fill record forms — the system should flag invalid values.

What's Important to Know

Field rules — on the editor Fields tab: Required, email, url, digits, json, etc.
Save-time validation — inline in the table or record card; invalid values are not saved and show a hint.
Import — Preview before import lists Invalid rows; critical errors block import until mapping or the file is fixed.
Complex cross-field rules (e.g. end time after start time) need advanced setup — see an integrator or the advanced options reference.

Prerequisites

You opened Menu → Custom Data.
Field rules are configured or you are preparing an import.

Validate while editing records

Open the table from Tables.
Add or edit a row (inline or Add row / record card).
Fill fields with rules (required, email, etc.).
Try Save — invalid values highlight and do not persist.
Fix values and save again.

Validate before import

Start Import data (guide).
Proceed to Preview before import.
Review the preview table and Invalid rows.
Fix mapping, field types, or the file — repeat preview until critical errors are gone.
Confirm import.

Configure rules in table structure

Edit the table → Fields tab.
Add or open a field → in the field card:
- enable Required;
- pick a semantic type with built-in checks (email, url);
- add Validation rules if needed.
Save the structure.

How to Verify

Invalid email or empty required fields do not save.
Import with bad rows shows them on preview and blocks completion when critical.
After rule changes, new records use updated checks.