¶ Overview
The system mapping template is an Excel spreadsheet designed to provide Clients with a simple method for providing their system fields. The template shows examples of moving a field from System A to System B (Source to Destination) and vice versa. Clients are not expected to provide all the possible fields or the API field names. Typically, we request that the client provide any custom fields and user-defined fields (UDF) that may not be included in the default Common Model mappings.
- Technology: Excel
- Sphere: Documentation
- SDLC: Discovery
- Cadence: Once
Connect Integration: Connect System A & B Mapping Template.xlsx
CEF & ERP Integration: Connect System A & B Mapping Template.xlsx
Payment Hub Integration: Payment Hub & ERP Mapping Template.xlsx
¶ Mapping Process
- On the worksheet named “Overview,” fill out the following fields:
- Client Name → [Client Company Name]
- System A (Blue) → ERP/CRM
- System B (Orange) → eCommerce/ERP/CRM
- Review the “Reference Example” sheet to demonstrate to clients how the mapping file should appear.
- The Source column is the system on the left, and the Destination column is the system on the right.
- Once the [System A] and [System B] Columns are changed, you will notice the names on each of the sheets (excluding the reference example) will also be updated.
- Once the [System A] and [System B] Columns are changed, you will notice the names on each of the sheets (excluding the reference example) will also be updated.
- Delete any sheets that are not relevant to the project.
- Feel free to rename the sheets if an entity type will be integrated.
- Feel free to rename the sheets if an entity type will be integrated.
- Save as and update the title name to reflect the updated System names:
- Provide the mapping template in a Basecamp to-do assigned to the client:
¶ Terms
- Available Fields: are any fields related to the specific integration sync (e.g. Sales Orders) that may be used during the project. Available fields include the table that the field are pulled from.
- Tables: are used to find fields that may exist within multiple tables. You can denote a table by combining the table and the field with a period (Ex: Table.FieldName).
- The Source: column can either be a property from the system or a "static"/"constant" value; denoted by wrapping the value in quotes (ex: See row 20 in the Reference Example sheet: "WEB").
- The Destination: column will always be the target property for the mapping between systems. Your destination may change when back syncing from one system to another.
- Lists: are used if fields can contain multiple values. You can denote a list by adding an [*] at the end of the field name (ex: See row 13 in the Reference Example sheet: Order.LineItems[*].Quantity)