Mapping

Created by Reachware Support, Modified on Tue, 17 Mar at 12:12 PM by Reachware Support

Data Mapping is the process of defining how information moves between systems in an integration flow.

Understanding Data Mapping

In Reachware Studio, mapping determines:

Which data should be extracted from a source system
How that data should be transformed if needed
Where the data should be placed in the destination system

You can think of mapping as the data navigation logic inside an integration flow. It guides each piece of information from its origin to the correct destination field.

Different platforms represent similar information in different structures. For example:

Source System	Destination System
CustomerName	customer_name
OrderDate	created_at
Items[]	order_lines[]
TotalAmount	order_total

Mapping ensures that each field from the source system is correctly matched to the corresponding field expected by the destination system.

Start Mapping

From the Flow Template, click the Mapping icon on the destination operation

The mapping popup appears with:

Source Data — Data from the first operation
Destination Data — Fields expected by the second operation

Professional Hint

Reachware gives you a quick way to start mapping your fields. You can click the Fill Destination button, which auto-populates all available destination fields based on the receiving system's expected payload format.

Data Types

Select the correct data type for each destination field:

Type	Description
String	Text
Integer	Whole numbers
Float / Double	Decimal numbers
Boolean	True / False
Date / Time	Timestamps
Array	Lists
Object	Nested structures

Mapping Types

One-to-One Mapping

Takes the exact value from the source and sends it to the destination with no transformation.

Source: customer_name = "Ali"
Destination: name = "Ali"

Use when: Direct data transfer without changes.

Hard-Coded

Ignores source data and sends a fixed value to the destination for every record.

Hard-Coded Value: "active"
Every record gets: status = "active"

Use when: Setting default values or constant fields.

Handlers Expression

Build custom logic to transform data using expressions or the Advanced Field Editor.

 if (source.value > 10; "Yes"; "No") 

Use when: Combining fields, calculations, or conditional logic.

Array Mapping

Used when the source data contains a list of objects and you need to map each item individually to the destination array field.

For more details, go to Array Mapping →

Field Settings

Click the Settings (⚙) icon on any mapped field to configure how empty values are handled.

Define Custom Empty Value

Check "Define Custom Empty Value" to specify a value that should be treated as empty.

Default empty values: "", null, [], {}

Action if Field is Empty

Action	Description
Skip field entirely	Field is not sent to the destination
Do nothing	Keep the value as-is
Use custom default value	Enter a replacement value (a required input field appears)
Use empty string	Replace with ""
Use null	Replace with null

Save and Exit

Click Save to apply your mappings
Click Exit to close the mapping window

Important: Unmapped required fields will cause errors during flow execution.