This article helps you fix common problems with transformations on exports, lookups, and import results in integrator.io. Each section starts with a symptom you can observe, such as missing fields, failed records, or rules that disappeared, and then gives the cause and the steps to resolve it. Use it when a transformation's output doesn't match what you expect.
Fields missing from Rules 1.0 output
Symptom: After you add a Rules 1.0 rule to change one field, the output contains only the fields that have rules.
Cause: Rules 1.0 builds the output only from its rules. Fields without a rule are dropped.
Resolution:
- Open the transformation, and confirm Rules 1.0 is selected.
- Add a rule for every field you want to keep. To keep a field unchanged, map it to the same name.
- Preview the output, and then save the transformation.
To keep the whole record and change only some fields, consider Rules 2.0 with JSON structure set to Modify input record { }.
Output fields missing for empty inputs
Symptom: A Rules 2.0 output field appears for some records but not others.
Cause: When the input field has no value, the default action, Do nothing, omits the output field.
Resolution:
- On the output field, select Settings.
- In Action to take if input field has no value, select a default, such as Use empty string as default value, Use null as default value, or Use custom default value.
Rules disappeared after you saved another option
Symptom: Rules you built in Rules 1.0, Rules 2.0, or JavaScript are gone.
Cause: A step applies only the option selected when you save. Saving in one option erases the rules in the other options.
Resolution: Rebuild the rules in the option you want to use, and save while that option is selected.
Prevention: Before you try a different option on a step that already has a transformation, copy the existing rules or script somewhere outside the editor.
Rules 2.0 isn't available on an import
Symptom: The Define transformation editor on an import step doesn't offer Rules 2.0.
Cause: Import-result transformations use Rules 1.0 or JavaScript.
Resolution: Build the import-result transformation with Rules 1.0 or JavaScript. For steps, see Transformation 1.0 rules or Transform data with JavaScript. To shape data before it reaches the destination application, use Mapper 2.0 on the import instead.
Records fail at a lookup field
Symptom: Records fail at a step that has a Rules 2.0 field with Field transformation type set to Lookup.
Cause: The input value has no match in the static lookup table or lookup cache, and If lookup fails is set to Fail record, the default.
Resolution:
- Find the input value in the failed record.
- Add the value to the static lookup's Edit mapping table, or to the lookup cache.
- If unmatched values shouldn't fail records, change If lookup fails to another action, such as Use null as default value. For every action, see Transformation 2.0 field settings.
- Retry the failed records.
A field fails data type validation
Symptom: An error displays when you save a Rules 2.0 field, and the field doesn't save.
Cause: The input data type can't be converted to the output data type.
Resolution:
- On the field's row, check the output and input data type selectors.
- Change one of them to a compatible combination. For valid combinations, see Data type validation.
Envelope values such as fileMeta are empty
Symptom: A JSONPath such as $.fileMeta.fileName, $.headers.<name>, or $.queryParams.<name> returns no value.
Cause: Input context is set to record, or the path's case doesn't match. Runtime data is available only in the envelope input context, and paths are case-sensitive. Header names are lowercase.
Resolution:
- In the Rules 2.0 toolbar, set Input context to envelope.
- Update each existing input path that points to record data so it starts with
$.record., for example change$.customerIdto$.record.customerId. - Check that each path matches the case in the Input pane, for example
$.headers.content-type, not$.headers.Content-Type. - Preview the output, and then save.
fileMeta is available only on file provider exports and lookups. For which steps provide each runtime object, see Transformation 2.0 input context reference.
Header or parameter values contain HTML entities
Symptom: A value written from a header or query parameter contains HTML entities, for example charset=utf-8 instead of charset=utf-8.
Cause: A handlebars expression with two braces, such as {{headers.content-type}}, HTML-escapes the value.
Resolution: Use three braces, for example {{{headers.content-type}}}, and then save the transformation.
Response header values don't reach later steps
Symptom: The transformation preview on an HTTP lookup shows the header field, but steps after the lookup don't receive it.
Cause: The lookup's results mapping is missing or doesn't match the transformation's output field.
Resolution: In the lookup's Results mapping, check the source field:
- It starts with
data[*].. - After
data[*]., it uses the transformation's output field name, such ascontentType, not the original header name, such asContent-Type. - It matches the output field name exactly. If you renamed the output field, update the results mapping.
For the full setup, see Use HTTP response headers in a transformation.
Auto-transform output fields is unavailable
Symptom: Auto-transform output fields is dimmed under Actions on the Rules 2.0 toolbar.
Cause: Auto-transform needs at least one output field that has no input field. It's unavailable before you add an output field, and after every selected field has an input field.
Resolution: Add the output fields you want filled, leave their input fields empty, select them, and then select Auto-transform output fields.