Managing Mapping Tables on M-Bridge – Kantata Knowledge Base

Overview

Mapping tables are used to pair different points or sets of data between two systems. For example, if a user in System A has a different name from the user in System B, the lookup table will link System A user's data to the specified user in System B. These tables can map a variety of items such as project statuses, fields on an object, or expense categories.

When setting up your mapping table, it's recommended to maintain a one-to-one mapping between systems. For example, if you map one object in Kantata OX to two objects in Intacct, it can cause integration errors, confusion, and incorrect data. However, there are certain scenarios where you can map multiple items from the source system to the same item in the target system depending on the integration.

Mapping Table Layout

An M-Bridge mapping table consists of two columns: Mavenlink on the left and External on the right. The Mavenlink column contains the object or value from Kantata OX and the External column contains the matching object or value from the integrating system.

Mapping Tables.png

Note: Some tables will have three columns with the third column indicating the direction of flow.

If needed, multiple values in the source system can be mapped to one value in the source system in certain circumstances (e.g. Expense Categories). Please note that this option is not supported for field mappings. Mapping one value in the source system to multiple values in the target system is not supported, including for two-directional mapping tables.

CSV Formatting

There are four available columns when uploading a mapping table via CSV:

Mavenlink Display Name
Mavenlink ID
External Display Name
External ID

These columns can be in any order but the column names must match the provided list.

Note: Certain integrations also have a Direction column.

Only the Mavenlink ID and External ID columns are required, but it is recommended that all columns are completed for every mapping table uploaded. The Mavenlink Display Name column contains the readable name that makes managing the mapping tables easier and the ID column sets the system IDs that the integration uses when transferring data to or from Kantata OX.

Note: All rows that have a Mavenlink ID must also have an External ID.

There isn't a limit on the number of rows that can be uploaded for a mapping table. However, the larger the table is, the longer it will take to load when importing and exporting.

Note: Please ensure that there are no empty rows in the middle of your CSV before uploading the mapping set.

How to Import a Mapping Set

Mapping sets can be created via a CSV upload to the integration platform. This makes the initial integration setup and continued maintenance more efficient.

Note: You can only import one mapping table at a time.

Log in to M-Bridge.
Locate the desired integration’s tile card and click the Settings button.
On the integration’s Scenarios page, click the Mappings button in the top-right corner of the screen and select your desired mapping set from the drop-down that appears.
On the Mappings page, click Import Mapping Set. The Import Mapping Set page opens.
Give your mapping a Name and select a Service from the drop-down.
Complete all other required fields. These will vary depending on which integration you are importing the mapping table for (e.g. the Organization field for the Xero integration).
Click Import. The table is imported.

How to Export a Mapping Table

Exported mapping tables can be edited and uploaded either as a new mapping table or as a replacement for an existing table. The exported CSV will contain all columns and rows of your mapping tables. If a table value was entered manually, the display name for that row will show as “manual input” with the system ID showing the inputted value.

Log in to M-Bridge.
Locate the desired integration’s tile card and click the Settings button.
On the integration’s Scenarios page, click the Mappings button in the top-right corner of the screen and select your desired mapping set from the drop-down that appears.
On the left side of the Mappings page, select your desired mapping table under the Mappings column on the left side of the page.
Click the drop-down arrow next to the Edit button and then select Export.
The mapping is exported and saved to your computer as a CSV.

How to Replace a Mapping Table

Replacing mapping tables works the same as importing a mapping table and has the same CSV requirements. If you have many scenarios, it may be more efficient to replace an existing mapping table than to create a new one and update all scenarios to use that new table.

Note: It's recommended to export an existing table before replacing it so you can use the export as a backup to restore in case the replacement table is incorrect.

Log in to M-Bridge.
Locate the desired integration’s tile card and click the Settings button.
On the integration’s Scenarios page, click the Mappings button in the top-right corner of the screen and select your desired mapping set from the drop-down that appears.
On the left side of the Mappings page, select your desired mapping table under the Mappings column on the left side of the page.
Click the drop-down arrow next to the Edit button and then select Replace
Click OK in the confirmation modal that appears. The Import Mapping page opens.
Click the Browse button and select the CSV file you want to replace the existing mapping table with.
Click the Import button to begin the replacement. You're redirected to the mappings page once the import is complete.