Page Comparison

...

Field Name

Field Type

Description

Label*

Default Value: Mapper
Example: Extract Employee Data

String

The name for the Snap. You can modify this to be more specific, especially if you have more than one of the same Snap in your pipeline.

Null-safe access

Default Value: Deselected
Example: Selected

Checkbox

Select this checkbox to set the target value to null if the source path does not exist. For example, $person.phonenumbers.pop() ->$ lastphonenumber might result in an error if person.phonenumbers does not exist in the source data. But, when you select this checkbox, the Snap does not display an error. Instead, it writes null to lastphonenumber.
If you deselect this checkbox, the Snap fails if the source path does not exist. The Snap either ignores the entire record or writes the record to the error view (based on the setting of the error view field).

Pass through

Default Value:Deselected
Example:Selected

Checkbox

Select this checkbox so the Snap passes all the original input data into the output document with the data transformation results.

If you deselect this checkbox, only the data transformation results in the mapping section appear in the output document and the input data is discarded.

Note

This setting is impacted by Mapping Root. If Mapping Root is set to $ and Pass through is deselected, anything not mapped in the table does not pass through. However, if Mapping Root is set to $customer and Pass through is deselected, it only applies to the items in the Mapping Root level. That means that anything above the Mapping Root level passes through and items at the Mapping level that are not mapped in the table do not pass through.

Expand

title	When to select Pass through

Always select Pass through if you plan to leave the Target path field blank. Otherwise, an error displays to indicate that the field you want to delete does not exist. This is the expected behavior.

For example, if you have an input file that contains a number of attributes and you need only two of these downstream. To accomplish that:

1. Connect a Mapper Snap to the downstream Snap.

2. List the two attributes you need in the Expression fields,

3. Leave the Target path field blank.

4. Select Pass through.

When you execute the pipeline, this Snap evaluates the input document/binary data, extracts the two attributes that you want, and passes the entire document/binary data through to the Target schema. From the list of available attributes in the Target Schema, the Mapper Snap picks up the two attributes you listed in the Expression fields, and passes them as output. However, if you do not select the Pass through checkbox, the Target Schema would be empty, and the Snap displays the No schema available error.

Transformations*

Use this field set to configure the settings for data transformations.

Mapping Root

Default Value: $
Example: $

String/Suggestion

Specify the subsection of the input data to map. Learn more: Understand the Mapping Root.

Input Schema

Dropdown list

Select the input data (from the upstream Snap) that you want to transform. Drag the item you want to map and place it under the Mapping table.

Sorted

Default Value: Selected

Checkbox

Select this checkbox to sort the input schema and the target schema. The sort options are:

All: Sorts both mapped and unmapped data.
Mapped: Sorts only the mapped data.
Unmapped: Sorts only the unmapped data.

Mapping table*

Use this field set to specify the source path, expression, and target path columns used to map schema structure. The mapping table makes it easier to:

Determine which fields in a schema are mapped or unmapped.
Create and manage a large mapping table through drag-and-drop.
Search for specific fields.

Learn more about : Use the Mapping Table.

Expression*

Default Value: N/A
Example: $first.concat(" ", $last)

String/Expression

Specify the function to use to transform the data. For example, combine, concatenate, or flatten. Expressions that are evaluated replace the source targets at the end of the pipeline runtime.

Note
The data from previous undefined Snaps in the Mapping Table pass through the Data Snap to the next Snap. However, when you define output fields in the Target Path, and if the field name is the same as a field name that would otherwise pass through, the field in the mapping table overrides the output.

Learn More: Understand Expressions in SnapLogic and Use Expressions for usage guidelines.

Expand

title	Managing Numeric Inputs in Mapper Expressions

When you work with upstream numeric data, you might see some unexpected behavior. For example, consider a mapping that reads as follows:

Expression: $num +100
Target path: $numnew

Now, the value passes from upstream for $num is 20.05. You expect the value of $numnew to now be 120.05. However, when you execute the Snap, the value of $numnew is shown as 20.05100.

This happens because, as of now, the Mapper Snap reads all incoming data as strings, unless they are specifically listed as integers (INT) or decimals (FLOAT). So, to ensure that the upstream numeric data is appropriately interpreted, parse the data as a float to convert the numeric data into a decimal, and all calculations on the upstream data in the Mapper Snap work as expected:

Expression: pareFloat($num1)+100
Target path: $numnew

The value of $numnew shows 120.05.

Target path

Default Value: N/A
Example: $FirstName

String/Suggestion

Specify the target JSON path where the value from the evaluated expression is written. For example, after evaluation of the $person.firstname expression, the Snap inserts the firstname for the person object.

Target Path Recommendation

Info
Iris simplifies configuring the Target path property in this Snap with suggestions for the Expression and Target path fields mapping. To make these suggestions, Iris analyzes Expression and Target path mappings in other pipelines in your Org and suggests the exact matches for the Expressions in your current pipeline. The suggestions display when you click the Suggestion icon in the Target path.

For example, you have the Expression $Emp.Emp_Personal.FirstName in one of your pipelines. You set the Target path for this expression as $FirstName. Now, if you use the expression $Emp.Emp_Personal.FirstName in a new pipeline, then Iris recommends $FirstName as one of the Target paths to help you standardize the naming standards in your org.

The following shows how Iris recommends the Target path in a Mapper Snap:

Snap Execution

Dropdown list

Select one of the three modes in which the Snap executes. Available options are:

Validate & Execute: Performs limited execution of the Snap, and generates a data preview during pipeline validation. Subsequently, performs full execution of the Snap (unlimited records) during pipeline runtime.
Execute only: Performs full execution of the Snap during pipeline execution without generating preview data.
Disabled: Disables the Snap and all Snaps that are downstream from it.

...

Versions Compared

Old Version 85

New Version 86

Key