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

Map data between external systems and iPaaS.com

Updated over a week ago

Dashboard

  1. Search: Search or filter for the desired mapping.

  2. Add New Mapping Collection: To create a new mapping (see following page for more details).

  3. Active/Inactive: Change to see inactive or active mappings.

  4. Type: Data Model (and child) where this data will be mapped to.

  5. Parent Record: Mapping at the parent level.

  6. Name: The name given by the user or integrator. As a best practice, it should be named in the following format:
    [APPLICATION] [DATA MODEL] [ADD/MODIFY/DELETE] [FROM/TO] IPAAS

  7. Count: The number of fields in that mapping.

  8. Child Record: Mapping at the child level.

  9. Clone: Duplicate the mapping.

  10. Reverse Clone: Clone the mapping that flips the direction and field mappings.

  11. Add Child Collection: Add a child mapping collection.

  12. Edit: Edit this collection (see details on next page).

  13. Delete: Delete the mapping.

Add a New Mapping Collection

  1. Type: Data Model (and child) where this data will be mapped to. This is NOT limited to the data types supported by the subscription nor by enabled webhooks.

  2. Parent Record: Mapping at the parent level.

  3. Name: The name given by the user or integrator. As a best practice, it should be named in the following format:
    [APPLICATION] [DATA MODEL] [ADD/MODIFY/DELETE] [FROM/TO] IPAAS

  4. Sync Type: The sync type tells iPaaS.com what to do when there is new or updated data in the mapping collection.

  5. Collision Handling Method: Options for how iPaaS deals with duplicate records on this mapping.

  6. Description: The description of the mapping.

  7. Mapping Filter: Allows users to use C# to filter out items that are not needed or are not ready for iPaaS.com or the destination system.

  8. Error Filter: Allows users to use C# to trigger errors based on the data in this mapping collection.

  9. Direction: Is this to or from iPaaS.com.

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

Edit Mapping Collection

These are the base settings for a mapping:

  1. Name: The name given by the user or integrator.

  2. Sync Type: The sync type tells iPaaS.com what to do when there is new or updated data in the mapping collection (see next page).

  3. Parent: If this is a child record the parent would be specified here.

  4. Direction: Is this to or from iPaaS.com

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

  6. Collision Handling Method: Options for how iPaaS deals with duplicate records on this mapping.

Sync Type

The sync type tells iPaaS.com what to do when there is new or updated data in the mapping collection:

  • Add: Add the new data.

  • Update: Update any existing data.

  • Add/Update: Either adding or updating data.

  • Delete: Delete the data.

  • Delete Triggered Update: Action that happens when iPaaS.com is passed a delete command from another system.

Filters

These are the base settings for a mapping:

  1. Mapping Filter: Allows users to use C# to filter out items that are not needed or are not ready for iPaaS.com or the destination system.

  2. Error Filter: Allows users to use C# to trigger errors based on the data in this mapping collection.

  3. Description: The description of the mapping to communicate to other iPaaS.com users the intent of the mapping.

Note: Errors that are due to an error filter will not automatically retry.

Mappings List

  1. Quick Add: Allows a user to to add a new mapping with limited fields. (not shown)

  2. Add New Mapping: Allows users to add a new field in the new field modal. (see next page)

  3. Mapping Type: Specifies the type of mapping which will hide or show other options.

  4. Source: The field, formula or value of the source data. Depending on the direction of the mapping this could be iPaaS.com data or data from the external system.

  5. Destination: The destination field for this mapping.

  6. Edit: Edit the mapping. (see following pages)

  7. Note: A note about the mapping. Useful for documenting a dynamic formula.

  8. Delete: Delete the mapping.

Edit/Add Mapping Types

Field

  1. Types: To see the following fields, field is selected.

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

  3. 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.

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

  5. 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.

Default

  1. Types: To see the following fields, field with default is selected.

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

  3. 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.

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

  5. 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.

  6. Default: Allows for a default value to be passed in if the source data is not present.

Static

  1. Types: To see the following fields, static is selected.

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

  3. 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.

  4. Source: A static value to add to the destination field.

Lookup Translation

  1. Types: To see the following field, lookup translation is selected.

  2. Lookup Collection: Select the lookup translation to reference for this mapping field. The collection must already be created to be referenced here (see below).

Dynamic Formula

  1. Types: To see the following fields, dynamic formula is selected.

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

  3. 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.

  4. Source: Used for C# to specify a formula to add to the destination field.

  5. Validate: Click to validate the code entered.

Translations

Translations are collections of pairs of data that match a set of data from one system to data in iPaaS.com. In the below example, you can see the order statuses in one system and how they have been slimmed down. The advantage of this type of mapping is that it can be easily editable.

Dashboard

  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.

Add/Edit Translation Collection

  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.

  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 Translation Lines

Related Articles
Why iPaaS.com?
Hub & Spoke Approach
Overview
Subscription Configuration - Webhooks (External)
Export Mappings
Did this answer your question?