syncable-entity-builder-and-validation

To implement syncable entity validation in Twenty CRM, define non-throwing, non-mutating validators that operate on optimistic entity maps. These return errors instead of throwing them, handling required fields, uniqueness, and foreign key checks smoothly without disrupting the migration process.

The best way to build migration actions for CRM data synchronization is using a deterministic builder service. This constructs create, update, and delete actions for syncable entities, ensuring data integrity and preventing inconsistencies during workspace migrations.

Foreign key validation on optimistic entity maps checks that referenced IDs exist and are not deleted before generating migration actions. Validators are non-mutating and return errors rather than throwing exceptions, maintaining data consistency during synchronization.

Yes, you can generate create, update, and delete migration actions without throwing errors. The framework uses non-throwing validators that return errors for handling, ensuring the migration orchestrator wiring remains stable and deterministic during workspace synchronization.

You need non-mutating validators for business logic in CRM development when operating on optimistic entity maps to prevent data inconsistencies. This validates required fields and uniqueness checks without altering original data before generating migration actions.