Prefix transform function

Introduction

The prefix transform function is used to add characters to the start of a given string field. For example:

[
    {"SKU": "RED001"},
    {"SKU": "RED002"},
    {"SKU": "BLUE001"},
    {"SKU": "BLUE002"},
    {"SKU": "GREEN001"},
    {"SKU": "GREEN002"}
]

...might become:

[
    {"SKU": "AW25-RED001"},
    {"SKU": "AW25-RED002"},
    {"SKU": "AW25-BLUE001"},
    {"SKU": "AW25-BLUE002"},
    {"SKU": "AW25-GREEN001"},
    {"SKU": "AW25-GREEN002"}
]

Adding a prefix transform

1

Edit map shape settings

In your process flow, access settings for your map shape. For example:

2

Access transforms for the required mapping

Locate the mapping rule that you want to update (or add a new mapping rule), then click the transform button. For example:

3

Add a new transform

Click the add transform button. For example:

4

Select the prefix transform function

Click in the name field to access a list of all available transform functions, then select prefix from the string category. For example:

5

Enter your required prefix

In the prefix field, enter the characters that you want to append to the start of any source values for the source field. For example:

You can enter static text and/or flow/meta variables.

6

Confirm the source field to be transformed

Click the add field button:

...then click in source fields and select the source field to be used for this transform:

7

Confirm transform settings

Accept your changes (twice), then save the transform.

Using variables in prefix transform values

You can include flow or meta variables when defining prefix values. Some examples are shown below.

Prefix value
Variable value
Incoming value
Output value
AW25-

N/A

RED001
AW25-RED001
{{flow.variables.season}} 

season : AW25

RED001
AW25RED001
{{flow.variables.season}}-

season : AW25

RED001
AW25-RED001
[[meta.month]] 

month : JUNE

RED001
JUNERED001
[[meta.month]]-

month : JUNE

RED001
JUNE-RED001

Currently, it's not possible to combine flow and meta variables in a prefix value. This is a known issue to be addressed in a future release.

Last updated