Articles in this section

Transformations 2.0: Field settings

Output field settings

Click the Settings (settings_gear.svg) button to the right of the output field to configure additional settings.

Output data type: displays the selected data type for the output field you are mapping. Select a different value to change the data type. If you get an error message, you can attempt to validate your data type.

Output types: Select the type of field you want to apply to the ouput record. The types available change depending on the data type you select.

19066961767067-Output settings.png

The following field transformation types are available for each data type.

Output data type

Field output types

  • Copy an object array as-is from input data

  • Create object array in transformation

Standard

Send the value of the input field as the value in the output field. This is the default setting, indicating that data found in a specific field in the export should map to its corollary in the import application (1:1 direct mapping).

Hard-coded

Set the source field to a defined value for the destination field. Use this setting if you prefer to have the same value written to this imported data field for every record, regardless of the exported value.

How would you like to hard-code the value?: Select one of the following options:

  • Use custom default value: Inserts custom string value

  • Use empty string as default value: Inserts empty string

  • Use null as default value: Inserts null value

Custom value: Enter the value to send to the destination field. This field only displays if you choose Use custom default value from How would you like to hard-code the value?.

Handlebars expression

Build a handlebars expression for the value in the input field to send to the output field.

Handlebars expression: Enter a simple handlebars expression in the field, or click (pencil_handlebars.svg) to open the Handlebars advanced field editor (AFE).

Lookup

If you already know how a specific field value from the input application data should be replaced before being sent to the output application, then you can use a static lookup or lookup caches to define how each value should be replaced.

A. Define a static value-to-value mapping

For each Input field value, define the corresponding replacement Output field value that will be sent to the destination application.

Output field value: Enter the value as it would be replaced when sent to the output application.

Input field: The input field name.

Input field value: Enter the corresponding value that this field uses in the input data. You can also use {{handlebars}} expressions and add multiple values seperated by commas.

Note

An additional empty line is added to the list with each new value you add, and you can click Delete (trash.svg) on the right to delete any line.

Lookup name: Give the lookup a unique name so that it can be easily identified for use in other flows. You can also select any static lookups used in other flows.

If lookup fails: If no match returns from the lookup search, the record fails by default. integrator.io marks the record as failed and does not transfer any data for that record. You can select one of the following alternative options if needed:

  • Do nothing: The field and value is skipped.

  • Fail record (default): integrator.io marks the record as failed and does not transfer any data for that record.

  • Use empty string as default value: Inserts empty string.

  • Use null as default value: Inserts null value.

  • Use custom default value: Inserts custom string value.

B. Define mapping using lookup caches

If you're using a lookup cache to define the mapping, enter values for the following fields:

Lookup cache name: Enter a part of the name or the full name to search and find an existing cache. If you want to create a new cache, provide a unique and meaningful name.

Lookup cache value field: Select a field path (provided in JSON notation) to map the destination data. With the lookup cache key as a reference, this path value is a unique identifier to map the data.

If lookup fails: If no match returns from the lookup search, the record fails by default. integrator.io marks the record as failed and does not transfer any data for that record. You can select one of the following alternative options if needed:

  • Do nothing: The field and value is skipped.

  • Fail record (default): integrator.io marks the record as failed and does not transfer any data for that record.

  • Use empty string as default value: Inserts empty string.

  • Use null as default value: Inserts null value.

  • Use custom default value: Inserts custom string value.

Output field is date field

Check this box if the output field requires a date format. Additional date field options display if this box is checked.

Date field options

Input field date format: Select the date format for the input field.

Input field date time zone: Select the time zone for the input field.

Output field date format: Select the date format for the output field.

Output field date time zone: Select the time zone for the output field.

Input field and Input data type

Input field: This field is automatically set if you have already mapped an input field in the Transformations 2.0 panel. If you are adding a new field, you must also assign the Source data type.

Input data type: If you have already selected an Input field, the data type is automatically set. If you added a new input field, use the drop-down list to set its data type.

Action to take if input record field has no value

Select one of the following options when the mappings return an empty value. The options available vary according to data type, and the behavior of each selection varies according to which version (Transformations 1.0 or Transformations 2.0) you use to map your fields.

Data type

Action to take if source record field has no value

Transformations 2.0

string

Use empty string as default value

Inserts empty string

Use null as default value

Inserts null value

Use custom default value

Inserts custom string value

Do nothing (default)

Removes field name and value

number

Use empty string as default value

Inserts 0

Use null as default value

Inserts null value

Use custom default value

Inserts custom number value

Do nothing (default)

Removes field name and value

Boolean

Use empty string as default value

N/A

Use null as default value

Inserts false

Use custom default value

Selects true or false

Do nothing (default)

Removes field name and value

object

Use null as default value

Inserts null value without object formatting

Do nothing (default)

Removes field name and value

[string]

Use empty string as default value

Inserts empty array

Use null as default value

Inserts null value without array formatting

Use custom default value

Inserts custom values as array ["a", "b", "c", "d"]

Do nothing (default)

Removes field name and value

[number]

Use empty string as default value

Inserts empty array

Use custom default value

Inserts custom number values as an array [1, 2, 3, 4]

Use null as default value

Inserts null value without array formatting

Do nothing (default)

Removes field name and value

[Boolean]

Use empty string as default value

Inserts empty array

Use custom default value

Inserts custom values as an array [true, false, false]

Use null as default value

Inserts null value without array formatting

Do nothing (default)

Removes field name and value

[object]

Use null as default value

Inserts null value without object formatting

Do nothing (default)

Removes field name and value

Settings description: Enter an optional description of the settings configured for this field.