Skip to main content
All CollectionsSubscriptions Management
Subscription Configuration - Manage Translations
Subscription Configuration - Manage Translations

Add support for a translation table that lives within your mappings

Updated today

Manage Translations Dashboard

  1. Add New Translation Collection: To create a new translation collection.

  2. Active/Inactive: Change to see inactive or active translations.

  3. Type: Data Model (and child) where this data will be translated for.

  4. Name: The name given by the user or integrator for this translation. As a best practice, it should be named in the following format:
    [APPLICATION] [DATA MODEL] [TYPE OF DATA] [FROM/TO] IPAAS

  5. Count: The number of values in that translation collection.

  6. Edit: Edit this record.

  7. Delete: Delete the record.

  8. Clone: Clone this record.

  9. Reverse Clone: Clone the translation that flips the direction and translation values.

Add Translation Core Record (Top of page)

  1. Name: The name given to the translation.

  2. Type: The data module or child that this translation is associated with.

  3. Sort Order: Defines where this will show in the list. The lower the number the higher it will live in the list.

  4. Direction: Is this going TO or FROM iPaaS.com.

  5. Destination: Choose if this data will be in a field or custom field.

  6. Field Selection for Destination: Visible fields are based on the mapping collection type (which pulls from the data model) and the direction. If the direction is TO iPaaS.com, these fields are iPaaS.com fields. If the direction is FROM iPaaS.com then these fields are from the subscription.

  7. Source: Choose if this data will be in a field or custom field.

  8. Field Selection for Source: Visible fields are based on the mapping collection type (which pulls from the data model) and the direction. If the direction is TO iPaaS.com, these fields are subscription fields. If the direction is FROM then these fields are from iPaaS.com.

Translation Records

  1. Source: Name of the value for the source value.

  2. Destination: Name of the value for the destination value.

  3. Edit: Edit the lookup translation.

  4. Delete: Delete the lookup translation.

Add/Edit Lookup Translations

Lookup translations are the values and corresponding mappings associated with the translation.

  1. Mapping Type: Lookup Translations support Field and Dynamic Formula types.

  2. Destination: The value in the destination system.

  3. Source: The value in the source system.

  4. Sort Order: Defines where this will show in the list. The lower the number the higher it will live in the list.

Related Articles
Overview
Subscription Configuration - Manage Mappings
Export Mappings
Integration Settings
Did this answer your question?