< Back


Now that we have configured our station and are ready to send data to our target system, we have to configure what we actually want to send.


A datamap contains information on what kind of data to load from your system and how to format it for the export.
You could compare a datamap to a loading plan, which describes what kind of cargo to put on your export train.
Or in simpler terms:

  • Station = Where to shall it be exported?
  • Job = What and when shall be exported?
  • Datamap = How shall it be exported?


When creating the station, the connector should already have created a new datamap.
Open the datamap-configuration inside the component overview now.
You should see an editor similar to this one:


Click here to return to the component overview.

Duplicate Datamap

This button allows you to duplicate this datamap. This can be useful for quickly trying out changes without editing the original datamap.

Import / Export

You can create and import backups using these two buttons.
You can only backup a single datamap here. Alternatively you can back up the station which includes all associated datamaps.

Datamap Summary

This button will open the dialog for creating a datamap-summary as PDF.

Basic Settings

These settings shall be available for all connectors.

Label Description
Label This is the name of the datamap.
Key This is the external key of the ContentServ record. You can leave it as is.
Run as User You can override the user for all exports which use this datamap. If no user is specified, the currently active user (logged in or set in active-script) will be used.
SAWSConnector This setting displays the connector of this datamap.
Description You can describe what this datamap is used for here.
Format This is an old ContentServ field which specifies the return value of the rest-serice.
You can simply ignore this value.
Default Language This language will be used for the logs.

Data Source

Using the Data Source setting you can select a reader plugin.
Depending on the reader, you can load the raw data for your export from different Systems (PIM / MAM) or using different methods (SC::Channel / Views).
The reader also influences the available nodemaps (more on that later) and may add a plethora of additional options.
Some connectors may also expand the available options for their readers.
You can find information about them in the category “Readers”. (click)

Language Mapping

The language mapping is used to configure the languages of your export.

Label Description
Source language Select a language from your ContentServ system to read the data from.
Target language Enter a key you want to use for this language when exporting.
Where exactly this key will be used depends on your connector.
Channel You can select an SC::Channel here.
For basic exports, this can stay empty.
Our PIM-extensions are covered in a seperate turorial.
Currency Select a currency for the SC::Price export here.
For basic exports, this can stay empty.
Our PIM-extensions are covered in a seperate turorial.
Stock Enter which stock source you want to use for stock exports.
For basic exports, this can stay empty.
Our PIM-extensions are covered in a seperate turorial.

Limiting PIM / MAM Access

When exporting from items (products, views, mamfiles) you have to grant access to parts of your PIM or MAM.
Return to your station configuration and select the tab “Data Sources”.
Under “Root nodemaps” the requested views, products or mamfiles you want your datamaps to be able to export.
This option only specifies what you are able to export. The actual items to be exported are selected in the job.
Jobs are covered in a seperate tutorial.

Mapping table

Now that we’ve covered the base configuration, it’s time to explore the heart of the SAWSConnector.
Because each PIM-structure and each target system is different we had to design a system capable of changing the data structure based on the target system.
The mapping tables allow us to do exactly that.

This tutorial will use our SimpleExcel connector for it’s easily readable output.
If you’re connecting to a shop system like Magento or Shopware you need a minimum configuration for these system to accept your export.

You will find the neccesary information to configure these systems in the manual corresponding to your connector.


Each nodemap specifies input values, output values and a transformation.
Different Nodemaps are usually used for different export types (e.g.: a datamap for uploading categories and one for products).

Disable Rows

Use these switches to skip rows when exporting. This feature is useful for troubleshooting.


This column is used to select the source of a single data point.
For items (products, views, mamfiles) this is either a native value like their ID / label or a CONTENTSERV attribute you configured in your PIM / MAM.
You can select it by clicking the little arrow and choosing your attribute in the dialog that will open.

Alternatively you can search available attributes and values by clicking inside the field and hitting Ctrl + Space or just writing what you want to use.

Target Column

Here you can enter which key to use for your selected value.
Connectors for Excel, JSON or XML will allow you to enter any custom value, while systems like Shopware or Magento have fixed APIs which require specific values and keys.

Just like the attribute field, the connector will try to support you in finding the correct key.
Here you can see an example from our Shopware 6 connector:


This column allows you to modify the value during the export.
Format plugins are covered in a seperate tutorial.
To simply export a value, you can choose Formatted Value or Unformatted Value.

Duplicate Rows

Use this button do duplicate a row.
Duplicating might prove useful if you configured a complicated transformation you want to use for several attributes.

Import / Export Row

As with stations and whole datamaps, you can create and import backups of single rows.

Additional Options

Some connectors offer additional options for rows. These are neccesary to use the full capacity of the target system.
To learn about what these options do, please consult the manual of your specific connector.

Example Mapping

Here’s an example mapping taking from our SimpleExcel-Connector:

An export using this datamap generated the following output:

Was this article helpful?
How can we improve this article?
Please submit the reason for your vote so that we can improve the article.
Previous Station configuration
Next Importing templates
Table of Contents