In the Import Mapping tab under Connect, you will find a list of ‘Omnia Connect Fields’. These are the main fields that Omnia needs to process the data. Therefore the fields from your internal data source should be aligned to the Omnia standards in order to process your data. Which of these fields are required depends on which of the Omnia modules you will be using. (Required fields)
If you want to map the fields from your internal data sources to any of the Omnia Connect Fields, follow the steps below.
Step 1 Go to Connect > Import Mapping
You can only map your fields when the data feed(s) are connected. If you have recently made changes in your data feed(s) or added new feed(s) start by clicking on the "Update feed data" before starting with mapping fields in Omnia.
Step 2 - Select a field
After having connected your feed(s) under the tab ‘Configure feeds’, you can begin mapping the fields under the tab ‘Import Mapping’.
- Click on the field you want to map. In this example, the first field - ID - is selected.
Step 3 - Select the corresponding field from (one of) your connected data feed(s).
After clicking on the search bar, a drop-down will be shown automatically. Here you can select one or multiple fields (when using a formula) from the connected feed that you want to use in the mapping of the Omnia ID field. In this example, feed field [ProductID] is chosen. Keep in mind that the goal of import mapping is to adapt your data fields to Omnia's data structure, so connect the fields that are (most) similar.
Move your mouse over the blue and green import fields to see more information about every field.
Step 4 - Specify the Value Type(s) of the used field(s)
After having selected the field from your feed, it must be specified what is the Value Type of the field. Even though Sample value that is shown (12345) looks like an integer, there might be other [ProductID] values that contain text. Additionally, we are not subjecting the field to any mathematical functions. Therefore, it is best to choose ‘Text/String’ for this field.
There are several options to choose as value type:
- Text (string)= all variables with text included but also numbers that don't have a calculation purpose, like GTINs or product ID numbers.
- Number (decimal)= numbers like prices, margins etc. (all numbers that are used for calculations or in Omnia calculations)
- Number(Int64/int32)= Numbers that can only be integers. (e.g. amount of stock or units sold)
- Boolean= values that can only be true or false (0 or 1). (e.g. when you want to indicate that a product is in stock or out of stock.)
Step 5 - Test the mapping for errors
Before being able to save the mapping, you have to test whether it is able to run. The ‘Sample’ value from ‘1. Define value’ is automatically inserted as the ‘Test value’ in ‘2. Test and validate value’. If you wish to change the ‘Test value’ you can delete ‘12345’ from the box, replace it with another value.
Click ‘TEST (BEFORE SAVE)’ to continue
Step 6 - Save mapping
After clicking the ‘TEST (BEFORE SAVE)’ button, the test result will be shown below. In the example, the indication is ‘SUCCESS’ and the resulting output is ‘12345’ (shown directly left of the Test button). Since the input is also ‘12345’ (the Test Value) and we do not want to make any modification to this value, we can conclude that the mapping works as intended. Now the mapping can be saved.
Click ‘Save’ will save the mapping and close the pop-up