< Back

Add and configure a new source data set

In order to add stations and jobs, you first need to create a source data set. A source data set is the basic configuration of your synchronization efforts and can be used for several stations (=satellite systems). The advantage is that you only have to configure basic settings once and can use them multiple times.

Navigate to the SAWSConnector module. You can add a new source data set by clicking on the “station overview” button of a station:


The station overview will open up. It displays the chosen source data set on the left handside, all existing jobs in the middle and the station on the right handside of the window:


In order to add a new source data set, click on “Add new source data set” on the upper left handside of the screen:


You will be taken to a mask asking you to enter the name of your new source data set:


Enter a name and click on the “Save” button:


The dialogue will reload and extent by further settings and the additional tab “Mapping tables”:


Configuration of the data source



This section lets you configure both workflows and attributes. Select all PIM View workflows you wish to be considered for the synchronization. Any workflow state you do not select will not be synchronized. Following that, choose the attributes or attribute sets (classes) you wish to synchronize to your Magento shop. If the attribute set class has childs, then you have to select them too! You can use the dialogue chooser for attribute sets or add attributes manually in the field below. Manually added fields must be separated with the pipe sign “|”.

Store View Mapping

StoreViews in Magento manage different language versions of a shop. The available language versions of products in the CONTENTSERV PIM need to be mapped to the relevant stores to ensure that language-specific data are syncrhonized to the correct StoreView. The SAWSConnector provides a simple mapping table:


Enter the StoreView codes as defined in your Magento backend. Navigate to System –> Manage Stores to see the overview of all StoreView codes set for your websites:


By clicking on the “+” sign in the Store View Mapping, a data chooser dialogue will open up where you can assign languages. Choose the standard language for the default StoreView in Magento. The table can be extended indefinitely for additional languages.

Workflow State Mapping

You can also define what CONTENTSERV PIM View workflow status should become what product status in Magento. The source data set offers another simple mapping table for that purpose:

Click on the “plus” button to add more lines to the table. Several CS statuses can be selected for Magento online or offline.

Attribute mapping

Ultimately, every CONTENTSERV PIM field that contains data that your Magento shop needs must be mapped to its Magento counterpart. We created another mapping table for that. Click on the tab “mapping tables” on the upper left handside of the screen:

Standard attribute mapping

You can find the standard attribute mapping in the first section of the mapping table tab:

This section is added automatically to your source data set as soon as you set the desired application (in this case: Magento). The section contains all mandatory fields of Magento – synchronization without the mapping of these attributes would fail. Additionally, we provide you with the attribute codes for crosssell, upsell and related products. We already provide you with the relevant Magento attribute code. All you need to do is set the CONTENTSERV counterpart field.

Additional attribute mapping

Additionally, if you set attributes in the “Configuration of the data source” section on the first tab of the source data set, all selected attributes will be displayed here as well.

Your mapping table could look something like this when you are done:

Help for the mapping table

Help for the default mapping table


Help for mapping of additional attributes


Was this article helpful?
How can we improve this article?
Please submit the reason for your vote so that we can improve the article.
Table of Contents