Flatten Transform Change Notice
The Flatten Transform in previous versons would create inconsistent results.
The inconsistency resulted when a child transaction type had no records:
- If there were a filter transform prior to the flatten transform where the filter deleted all the child records AND that child transaction type was one of the children participating in the flatten transform the transform would join the parent to an empty child record where the fields from the child transaction type would have empty values.
- This behaviour is similar to the ‘Use Strict Join Logic’ deselected.
- Conversely if the flatten transform has a transaction type where there were no child records but there were no filter transforms prior to the flatten transform, the transform would drop the parent record as it could not join to a child record.
- This behaviour is similar to the ‘Use Strict Join Logic’ deselected.
Integrations with Flatten transforms will continue to use this logic. An option will be displayed on the Flatten transform to use the logic introduced in this version.
This option cannot be re-enabled if the option is deselected and the transform saved.