< Back

Export several values simultaneously


With the plugin “SC::Complex-Export several values simultaneously” you can define a variety of attributes to be considered for a dynamic count-up of the target key.

One rather common use case is that there is a group of attributes (for example, all technical attributes) that need to be exported in dynamic pairings. Imagine you have 50 technical attributes and you need both their ID and the relevant values of these attributes in your export – and the target keys must be named dynamically, depending on the count of attributes.

Here is an example: “attribute_key_x” could be the ID of the attribute, “value_x” is the value that is set for that attribute. The usecase above describes that the count of the attribute defines a dynamic target key:

“SC::Complex-Export several values simultaneously” helps you define all the necessary parameters.


Set PdmarticleID as the source attribute in the data map (even if it is not the attribute you wish to export). For the target key, type any text you can think of, the target keys will be defined later in the process. Select the plugin “SC::Complex-Export several values simultaneously”.

Click on the gear-wheel button next to the plugin so the settings page will open up:

As of SAWSConnector version 1.7.x and higher, you can also use filters for the type of attributes to be considered and indicate a sort order for the export:



Value Description Example
JSON object Here you define the core of your target keys. The placeholder {count} will be replaced with the position in the reading order of the Connector (read further down for attribute order). In the “format section”, define the format plugin you wish to be carried out. The example shown above will export attributes to paired target keys of “TechnicalAttribute_X” and “CorrespondingValue_X”. For a definition of the plugin “SC::Special – Export value of current attribute, please click here.
Prioritized: Select the attributes directly. Sort order of the attributes here defines the priorization in output. This is the first option for you to define what attributes should be considered. You can set them directly from your attribute pool. The sort order you set them in here defines the priorization.  If you selected 3 attributes here and the first attributes contains values, the second one does not but the third attribute has a value, attribute 1 will “win”. Values in attributes 2 and 3 will not be considered for export.
 Or: LIKE Filter for ExternalKey of attributes, e.g. to export all “width” fields (e.g. SAP_WIDTH_%).  This is the second option for you to define what attributes should be considered. The filter will search through all ExternalKeys in your plattform’s attributes.  Set %text% to consider all attributes containing “text” somewhere in their ExternalKey.
 Or: Additional filter for tags of attributes  This is the third option for you to define what attributes should be considered. Set a tag to be considered – SAWSConnector will search for values in all attributes containing the tag you set here.  Set any tag you applied to the relevant attributes.
SAWSConnector version 1.7.x or higher: Filter attributes by this type You can set a filter for the SAWSConnector to only work with certain CS types. Set any attribute type, for example “Date” or “Chexkbox”.
SAWSConnector version 1.7.x or higher: Sort attributes by these columns Select the sort order in which you wish your attributes to be consideres. the sort order will always be ascending.  Sort by ID, ExternalKey etc.




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 Create a JSON-String
Next Format value lists
Table of Contents