Conflict Resolution Guide
Understanding and resolving transformation conflicts in projections. Covers type conversion issues, truncation risks, null handling, precision loss, and strategies for resolving each conflict type.
When a projection transforms properties from one representation to another, conflicts can arise. A conflict occurs when a property's source type, value range, or constraints are not fully compatible with the target representation. The projection editor detects these conflicts and guides you through resolution.
Conflict Types
How Conflicts Are Detected
The projection editor continuously evaluates each property mapping against the active profile's type system. Conflicts appear as visual indicators on affected properties, grouped by severity:
| Severity | Indicator | Meaning |
|---|---|---|
| Error | Red | The mapping will fail or produce incorrect results. Must be resolved before the projection is valid. |
| Warning | Amber | The mapping may lose data or produce unexpected results. Should be reviewed but will not block the projection. |
| Info | Blue | The mapping involves an implicit conversion that is safe but worth noting. No action required. |
Resolution Strategies
Type Conversion Conflicts
Truncation Conflicts
Null Handling Conflicts
Precision Loss Conflicts
Resolving Conflicts in Chained Projections
When projections are chained, conflicts can appear at any layer. A type override in an upstream projection may introduce a new conflict in a downstream layer. Always review the full chain when resolving conflicts, starting from the topmost layer and working downstream.