Skip to content

Flatten Transform Change Notice

The Flatten Transform in previous versions would create inconsistent results.

The inconsistency resulted when a child transaction type had no records:

  1. 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 Join Type set to Outer Join.
  2. 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 Join Type set to Cartesian (Strict) Join.

An integration built before this version goes on using the old logic, and Use V3 Logic on the Flatten transform reports that it is doing so. It appears on no other integration.

It is read-only. It says which logic the transform runs and cannot be changed there. In earlier versions it could be cleared, once, and never set again.