Conventions for Constructing Transformations

Last update: 2022-10-04
  • Created for:
  • User
    Admin
IMPORTANT

Read more about Data Workbench’s End-of-life announcement.

Table showing what conventions apply when constructing transformations.

Convention Description
Sequential execution

The transformations within a dataset configuration file are applied to the log entries sequentially (that is, in the order in which they are listed in the configuration file). Therefore, transformations must be listed in the order their outputs are used as inputs to other transformations. More specifically, if the output of one transformation is used as the input to another transformation, it is important for that former transformation to be listed prior to the latter transformation in the dataset configuration files. Otherwise, the data workbench server generates an error.

Processing stages provide a way to order the transformations that are defined within multiple dataset include files. For all of the dataset include files associated with a particular processing stage, transformations are ordered based on their inputs and outputs. In addition, if multiple dataset include files within a stage output data to the same field as a result of a transformation, the data workbench server generates an error.

For more information about stages, see Log Processing Configuration File, Transformation Configuration File, and Dataset Include Files.

A Transformation Dependency Map can display how a field is modified by a series of transformations. See Dataset Configuration Tools.

Output names Most transformations specify an output field. If the output is a user-defined extended field, the name for this field must start with "x-." The output field names cannot contain spaces or special characters. The names of extended fields can be written with mixed-case, such as "x-NewCampaignName," or "x-New-Campaign-Name" for readability, but they are treated by the software as case-insensitive.
Input fields

Input fields refer to one of the baseline fields or a user-created field resulting from the output of a previous transformation. If a constant string is needed, a quoted string can be used instead of a baseline or user-created field.

For a list of some of the commonly defined fields of data that the data workbench server can process, see Event Data Record Fields.

Simple strings and vectors of strings All transformations operate on strings and/or vectors of strings. Simple strings are literal sequences of characters. String vectors contain zero or more simple strings in a specific order.

On this page