Define what a valid record looks like
Create typed columns for text, numbers, dates, booleans, and JSON. Use required fields, defaults, uniqueness, and validation rules to make expectations explicit.
ART Datalake / Dynamic tables
Turn operational information into records your workflows can use. Define the shape of your data, connect related records, and evolve the structure as the business process develops.

Dynamic tables in practice
Create typed columns for text, numbers, dates, booleans, and JSON. Use required fields, defaults, uniqueness, and validation rules to make expectations explicit.
Column changes create schema versions. Existing records are validated when a typed schema is applied, so incompatible data must be reconciled before the change takes effect.
Model relationships between collections and make record changes available to event-driven workflows. Keep connected data consistent as applications read and update it.
Illustrative workflow
Keep supplier names, review states, and operational details in a table with defined fields. Link related records and use a change in review state as an input to the next workflow step.
Table deletion is a recoverable archive; permanent removal is a separate operation. Tables default to indefinite retention. Retention settings must also respect relationship constraints.
Yes. Schema changes are versioned and validated against the existing data. Incompatible records must be reconciled before a typed schema can be applied.
No. Tables hold structured records and relationships. Object storage holds files organized in buckets and folders. They support different parts of the same workflow.
Start with your workflow
Bring the records, files, and context behind your process. We’ll explore how Datalake fits.