Formats

Formats, formerly known as field plugins, are the core component of the SAWSConnector configuration that make it so flexible. Through the formats attribute values can be altered, checked, conditionally formatted, translated, shortened, and transformed in many other ways.

The format selection is located to the right of each data map row, and there are over 100 formats to choose from.

Choosing a Format

A data map row consists of the “Attribute”, “Target Key” and “Format”. The format controls in which manner the attribute value shall be extracted and processed before it is added to the export result. The attribute value is passed as the input value into the selected format.

These are the most commonly used formats, with hyperlinks to their respective articles.

Format	Description
CS::Formatted value	Extracts the display value of the given attribute.
CS::Unformatted value	Extracts the database/technical value of the given attribute.
Send configurable parameter value	Inserts a configured text value directly into the target key. Ignores the given attribute.
Replace strings via a transformation list	Replaces the attribute value via a transformation list.
Loop head (Configuration of loop values)	Creates a value loop for multiple values such as multiple DAM references.

Conditions

The conditions allow you to define exceptions in which the connector changes the processing logic. Read more about them here.

Placeholders

Placeholders are variables that can be used for any kind of value or logic in connector configurations. Read more about them here.

Settings

Formatting

The name of your format is displayed here. This value cannot be altered.

Name

You can provide a name for your format configuration here. Only use this feature if you plan to link to this format via the “Link to another configuration” option.

Status

The mapping status is used to mark data map rows and limit their validity. Read more here.

Debug format

(Since version 1.21.0)

This enables you to debug the format in Job Pilot. A detailed output of the input and result data will be displayed in the debug log entry. Note: This option should only be enabled temporarily while configuring the data map row. Otherwise, excessive logging will be created.

Format-specific Settings

Each format has its own custom settings. These settings are explained in the articles for each format.

Format of the result value

One format can follow another. The result value of the preceding format is used as the input value for the succeeding format. This is a very common use case.

Example: Using the transformation list format for removing the unit of the given attribute value and then multiplying it with the mathematical operations format.

Export language-dependently

Controls whether the attribute value shall be formatted language-dependently. This setting only works on formats if they are the first format in a data map row and not consecutive.

Option	Description
Setting from the attribute	The connector determines the language dependency of an attribute based on its type and settings. Selection attributes, for example, are always treated as language-dependent, even if the attribute settings are language-independent, because they may contain different values for each language since the value ranges are translated.
Yes	Attribute shall be treated as language-dependent.
No	Attribute shall be treated as language-independent.

This option has no effect in the DynamicJSON and GenericXML Connectors, because they process every data map row for every language anyways.

Was this article helpful?

1 0

How can we improve this article?

Please submit the reason for your vote so that we can improve the article.

Name

Email

Submit