Some of the Destinations do not refer to data that will be stored, but exist only to collect together values for other operations. While this may seem to add verbosity, it allows your control file to use the full data transformation and mapping features.

When viewing a Model in the admin UI, pseudo-destinations will be flagged, and their name will describe their purpose.

Loading other Destinations

To load an existing Destination for modification, or adding data in dependent destinations, a ‘load’ pseudo-destination must be set with information that identifies the specific object, followed by a load Instruction.

Note that control files for the User sync should not load or new any Destinations.

Structured values

Some values are structured, in that they are formed from multiple fields. For example, names of people are formed of their first and last names.

The model will include pseudo-destinations for each of the structured values used in the model, which are used to assemble the data, then store it in the actual Destination with the field-structured Instruction.