Best practices
Follow our best practices when starting a new project
Modeling Approaches
Use Cases
- Use Linked Projects
- Configure an incremental load
- Configure a multi-version load
- Configure a delete detection behavior
- Test a Generator upgrade
- Update a Project when the source changed
- Do a delta deployment
- Do a partial deployment
- Deploy a Project in production
- Take care of entries from Cleansing Error tables
- Reduce the volume of the Cleansing Error tables
- Avoid to load all data in development
- Optimize load performance
- Create a Date dimension
Business Rules
- Dataflow Sets amount (Business Rule)
- Dataflows amount (Business Rule)
- Relationships amount (Business Rule)
- Supported Term Mappings (Business Rule)
- Identity Terms amount (Business Rule)
- Identity Terms not nullable (Business Rule)
- Supported Implementation Types (Business Rule)
- Implementation Type Dataflows amount (Business Rule)
- Implementation Type Incremental Filter (Business Rule)
- Supported Deduplication Methods (Business Rule)
- Supported Load Cachings (Business Rule)
- Relationships from Link (Business Rule)
- Relationships from PIT (Business Rule)
- Foreign Key Mapping (Business Rule)
- Historized Source (Business Rule)
- ValidFromSourceTerm exists (Business Rule)
- ValidFromSourceTerm configured (Business Rule)
- Fact Load Strategy selected (Business Rule)
- One Fact Load Strategy selected (Business Rule)
- Effective Timestamp mapped (Business Rule)
- Business Key Terms not nullable (Business Rule)
- Business Key Terms amount (Business Rule)
- Supported Aggregation Types (Business Rule)
- Supported Historization Types (Business Rule)
- Supported Term Data Types (Business Rule)
- Terms amount (Business Rule)
- Dataflow Set Model Objects amount (Business Rule)
- Dataflow Sets Aggregation Amount (Business Rule)
- Supported Fact Load Strategies (Business Rule)
- Fact Load Strategy Insert needs Incremental selected (Business Rule)
- Dataflows amount with multi-version load (Business Rule)
- Supported Missing BK Behavior (Business Rule)
- Dataflow Sets amount with multi-version load (Business Rule)
- Deduplication with multi-version load (Business Rule)
- Aggregation with multi-version load (Business Rule)
- Supported Implementation Types for stage-driven load plans (Business Rule)
- No incremental load with a Deduplication (Business Rule)
- No deduplication for Stage objects (Business Rule)
- No Cyclic Dataflow (Business Rule)
- No Cyclic Relation (Business Rule)
- No delete detection with multi-version load (Business Rule)
- No delete detection source with a deleted set (Business Rule)
- Delete detection source exists (Business Rule)
- Delete detection source name is unique (Business Rule)
- Delete detection source Business Key exists (Business Rule)
- No delete detection with an incremental load in the source (Business Rule)
- Delete detection without historization set in the terms (Business Rule)
- Fact Load Strategy Dataflows amount (Business Rule)
- Model object has problematic characters in name (Business Rule)
- Model object has term with problematic characters in name (Business Rule)
- Model object has deduplication method PartitionOrder but no business keys defined (Business Rule)