- Show all articles ( 1 ) Collapse Articles
Owl Cloud Services
Shopware 5 Connector
Shopware 6 Connector
Source data set configuration
A source data set is the basic configuration of your snychronization 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 OXID Connector 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 OXID eShop. 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 “|”.
The following configuration manages the mapping of different languages to the shop languages. The available language versions of products in the CONTENTSERV PIM need to be mapped to the relevant languages in the OXID shop to ensure that language-specific data are synchronized to the correct language. The OXID Connector provides a simple mapping table:
Important is that the filed target language contains the abbrevation of the language in OXID
Workflow State Mapping
You can also define for each CONTENTSERV PIM View workflow status the target product status in OXID. 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 status can be selected for OXID online or offline.
In case you have variant articles, you cannot work with the above workflow status mapping. Instead you have to do the following:
It is necessary to map the workflow stateid for products and add a new value list for transformation.
You will find the ID of the workflow states under the settings. In this case you have to map the states of the channel view workflow (Oxid Channel Workflow) 149, 150, 151 and the relevant states of the product workflow (120: “Productive” -> “online”, 121: “Locked” -> “offline”), important for product variants.
Now add a new field status mapping for the “StateID” and use the “ProductWorkflowStatus” transformation list.
Take care in case of product variants. Add only the variant head to channel e.g. “UHD Nano TV”, see below. The variant head should extend related PIM product, then the table with article variants will be transferred to the shop automatically. For each article variant the status in the product workflow is relevant to manage the status in the OXID-Shop. For the variant head the workflow status of the channel is relevant.
Ultimately, every CONTENTSERV PIM field that contains data that your OXID shop needs must
be mapped to its OXID 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: OXIDeShop). The section contains mandatory fields of OXID – synchronization without the mapping of these attributes is possible but may fail. We already provide you with the relevant OXID 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:
The additional attributes are stored in the oxattribute database table in OXID. To have a mapping between Contentserv and OXID, a specific column CSEXTKEY is added to oxattribute database table. The key is defined in Contentserv in the mapping table in column Output Column.
With this, you can also connect existing attributes in OXID to attributes of Contentserv. You can also add or change the CSEXTKEY in the admin interface. Please note: for new attributes that are created by the OXID connector, the CSEXTKEY is set automatically.
Complex standard attribute mapping
Here are some mapping which can be more complex. These are described here.
oxvendors and oxmanufacturer
Relative path for MAM Files