Mapping is perhaps the most important step when setting up a task.
The purpose of this article is to familiarise yourself with that term and to learn how to effectively and precisely map the values you desire.
Mapping can be defined as an act of matching the fields of your Source Integration to those of your Target Integration.
It is a mandatory second-to-last step in every task, regardless of the Integrations used within that task.
However, the mapping section itself will differ on a case-to-case basis, based on the Integrations you chose as your Source and Target ones and based on the entities you chose to migrate.
Note: When we say the mapping section differs, we mean that Source and Target Integrations will have varying fields offered for mapping.
Methods and principles related to mapping remain the same, regardless of the Integrations / Entities used.
The field can be defined as a property (attribute) of a certain data type. Fields vary from app to app, which is why it is of paramount importance to map everything correctly.
E.G. You will have: email, first name, last name, and list as the available fields of SendFox to map when importing Contacts to SendFox.
However, another Integration that has Contact as an entity might have additional fields available for mapping, or some completely different fields.
Mapping section overview and basic rules
It is not possible to list every possible mapping variation in this article, seeing as how SyncSpider has well 200 native integrations.
We will, however, use several examples to better illustrate this process and see some "Dos and don'ts".
Sending Products from an online marketplace to Google Sheets
Let us first examine all the elements a mapping section has.
When first accessing mapping, you will be met with a screen similar to the one provided below:
You'll notice all the available Fields of your Source integration (in this case eBay) found on the left-hand side:
While the field of Target Integration (in this case Google Sheets) can be found on the right-hand side:
Mapping can be viewed as an act of dragging the fields from the left-hand side (source) and dropping them next to the corresponding fields from the right-hand side (target).
You'll notice that every time you map two fields, you get asked to set a Fallback value.
Fallback value serves as a replacement when not all source entries contain that value. It can be any text of your choice.
e.g. You don't know the salutation for each customer, so you set the fallback value to be "dear valued client".
Similar to Fallback value, Constant value can be mapped with any field for which we want one predefined value across all entries.
To learn more about the Constant Value field and its application, kindly head over to this Article.
Plugin Fields (extra fields in the certain system)
Some platforms such as Magento 2 or WordPress / WooCommerce have various plugins available to their users.
e.g. We fully support Magento 2's Amazon order IDs, thus allowing easy Magento 2 and Amazon synchronization.
We strive to modify our API schema to support as many plugins as possible for each of our integration modules.
However, if you are not seeing any fields related to the plugin you are using, kindly get in touch with our Support team and list the used plugins.
API schemas of the platforms we integrate with often require certain fields to be mapped for the task to work.
e.g. When sending Products from eBay to Shopify, Shopify would require fields such as Unique Identifier, Product Name, etc.
These fields have a small orange dot next to them:
Kindly note that there is another type of orange dot, albeit with a similar function:
These dots have an orange outline and are next to a collection of fields.
They signify the fact that if one field under that collection of fields gets mapped, that all of them would have to be mapped.
Otherwise, the collection of fields is not mandatory at all.
e.g. In the picture above, if we map the price, we would have to map currency, start date, and end date as well.
This option is found in the upper-right corner of the screen. It allows you to see what the end result will be for up to 5 data entries sent, without actually having to run the actual task.
Preview values not returning anything is a clear indicator that:
• there is no data present in the source
e.g. Order import method was an incremental report, and there aren't any new orders since the last task execution
• a connection with the source integration is intermittent, or incorrectly set up.
In those cases check and do the following before reporting this to our Support team:
1. Check if all permissions are granted to SyncSpider
e.g. did you set the read/write scopes for all the relevant entities
2. Check if anything was crucially changed on your end
e.g. Firewall or an additional layer of security was added to your platform that is blocking SyncSpider.
3. Refresh source/destination schemas (found under preview values)
4. clear your browser's cookies/cache
Collection means multiple attributes of the same type that are repeating.
When mapping a collection field, you will get the options to:
1. take first
If Take first value is selected, only the first attribute from the collection will be taken.
Similarly, if take last is taken, only the last attribute from the collection will be taken.
If take all is selected - one call record would be taken for each value. Sometimes this is exactly what you need, however, mapping collection fields with take all to "normal" fields can cause issues.
e.g. Mapping a price from collection to price in the same Order would create multiple Orders, instead of just one.
We hope you found this Article helpful :)
If you still have any questions or inquiries left unanswered, please don't hesitate to contact our Support via our website's chat widget, or get in touch with us on our Facebook page.
Our Customer Support Representatives will be more than happy to assist you.