Skip to main content
Prequel Import anticipates the case where Source Dataset schemas do not perfectly match target Destination schemas without some mapping and transformation. To support bridging between the two, Prequel supports a number of mapping and transformation options.

Who’s responsible for performing the mapping?

Prequel Import provides tooling to support both the Destination owner (you) to perform the mapping, as well as to expose this experience to your users. If you plan to embed this experience for your customers, please see the Customer Experience guide.
Dataset Mapping

Custom queries

At a full table level, custom SQL queries can be used to transform the Source data. This is a good solution for users that are comfortable with SQL, or who need aggregations or logic that spans multiple rows.

Mapping categories

Each Stream mapping has a field_type that determines how the target Destination field is populated. The two categories are summarized below.

Column mapping

A field mapping copies a Source column value directly into a target Destination field.

Column transformation

An expression mapping computes the target value from one or more Source columns using a formula (expression).
See the example below for a Stream that combines column and transformation mapping.
POST /streams

Expression syntax

Expressions use the expr-lang language. Any operator or built-in function from the expr-lang language definition is supported.

Additional supported functions

Prequel Import also provides the following additional helper functions for common transformations: