One type per source system
Creating ClientCRM, ClientERP and ClientSupport reproduces existing silos. Model Client, then retain the identifiers and mappings for each source.
The catch-all entity
An ObjetMétier type with dozens of optional properties hides rules and reduces quality. Separate concepts with different lifecycles.
One copy per department
Duplicating Client for marketing, finance and support prevents a shared view. Reuse the common type and verify the effective permissions for each use.
Every column becomes a property
Technical, calculated or temporary columns do not automatically belong in the business model. Keep only what has lasting meaning and use.
Fragmenting spaces
A space organizes a canvas; it is not a security boundary. Multiplying spaces without conventions makes shared concepts hard to find. Organize them by coherent domain; use workspaces and their access controls for isolation.
Confusing type and instance
ACME France is an instance of Client, not a new type. A type should accommodate multiple occurrences sharing the same structure.
Unnecessarily complex workflows or calculations
Do not use a workflow for a simple deterministic transformation. A calculated property or validation rule is easier to read and maintain.
A relationship instead of a property
Do not create a type for every simple value. A status without its own identity or properties should usually remain a controlled property.
