Skip to main content
Export Mappings

Access to your data, in the format you want, on demand

Updated over 5 months ago

Definitions

  • Export Mappings: Allows users to create an export of their data.

  • Scheduling Exports: These can be scheduled by using the events functionality by using the Event Type of Scheduled and the Name of the Events is Interval.

  • Export Translation: A utility to translate certain types of data to be then leveraged in the export mapping.

Note: iPaaS.com does not provide a FTP service so the customer will need to provide this.

Layout

  1. Search: Search or filter for the desired custom field.

  2. Add New Export Mapping Collection: Create a new mapping collection.

  3. Export Translation: See next section in this course.

  4. Active/Inactive: Change to see inactive or active exports.

  5. Type: The data module or child that this export is associated with.

  6. Name: Name for export mapping collection.

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

  8. Edit: Edit the export mapping collection.

  9. Delete: Deactivate this export mapping.

  10. Export: Run this export now.

Add New Export Mapping Collection

  1. Name: The name the user gives the eport mapping collection.

  2. File Name: The file name for the export.

  3. Description: A description the user can give the export.

  4. Filter: A filter in C# that can be used to filter out results.

  5. Export Type: This can be one of CSV, JSON or XML.

  6. Upload Type: This export can be placed on an external FTP Active, FTP Passive, FTPS, FTPES, SFTP or SFTP Key.

  7. Type: Select a data model that will include all children.

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

  9. Send Success Email: Should the system send an email if the export is successful?

  10. Success Email Dropdown: Will show emails that have been created and have this email type set.

  11. Send Fail Email: Should the system send an email if the export fails?

  12. Fail Email Dropdown: Will show emails that have been created and have this email type set.

Note: Once you save you can edit for additional fields and mapping (see below).

Edit Export Mapping

Header

  1. Name: The name the user gives the eport mapping collection.

  2. File Name: The file name for the export.

  3. Export Type: This can be one of CSV, JSON or XML.

  4. Upload Type: This export can be placed on an external FTP Active, FTP Passive, FTPS, FTPES, SFTP or SFTP Key.

  5. Host Name: The host name for the FTP.

  6. Port: The port for the FTP.

  7. User Name: The username for the FTP.

  8. Password: The Password for the FTP.

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

  10. Type: Select a data model that will include all children.

Emails

  1. Send Success Email: Should the system send an email if the export is successful?

  2. Success Email Dropdown: Emails that have been configured under the Email Templates with a type of Export.

  3. Send Fail Email: Should the system send an email if the export fails?

  4. Fail Email Dropdown: Emails that have been configured under the Email Templates with a type of Export.

Additional Fields

  1. Filter: A filter in C# that can be used to filter out results.

  2. Description: A description the user can give the export.

  3. Last Run Start Date: When the last export started.

  4. Last Run End Date: When the last export completed.

  5. Last Run Status & Message: The status of the last export.

  6. Export: Run an export now.

Mappings

  1. Quick Add: Allows a user to to add a new mapping with limited fields.

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

  3. Mapping Type: One of Field, Field With Default, Static, Lookup Translation, Dynamic Formula.

  4. Source: The source field for the data.

  5. Destination: Column heading in the export.

  6. Edit: Edit the mapping.

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

  8. Delete: Delete the mapping.

Export Mapping Types

Field

  1. Types: To see these fields, field is selected.

  2. Destination: Name of the field column in the export.

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

  4. Field Selection for Source: Visible fields are based on the type (which pulls from the data model).

Default

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

  2. Destination: Name of the field column in the export.

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

  4. Field Selection for Source: Visible fields are based on the type (which pulls from the data model).

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

Static

  1. Types: To see these fields, static is selected.

  2. Destination: Name of the field column in the export.

  3. Source: Used to specify a static value to add to the destination field.

Lookup Translation

  1. Types: To see these fields, lookup translation is selected.

  2. Destination: Name of the field column in the export.

  3. Lookup Collection: Select the lookup translation to reference for this field (see next below).

Dynamic Formulas

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

  2. Destination: Name of the field column in the export.

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

Export Translation Collections

Layout

  1. Add New Export Translation Collection: Create a new export translation collection.

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

Add

  1. Name: The name the user gives the translation collection.

  2. Type: Select a data model (or children).

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

  4. Destination Name: The column heading in the resulting CSV for this data.

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

  6. Field Selection for Source: Visible fields are based on the type (which pulls from the data model).

Did this answer your question?