Input 

Document

• Min: 0

• Max: 1

• Mapper Snap

• Binary to Document Snap

• Sort Snap

Optional. Use upstream Snaps to pass the dataset name.

Output

Document

• Min: 1

• Max: 1

• Mapper Snap

• Join Snap

• Union Snap

Documents in the dataset.

Label

String

Specify a 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.

N/A

Adobe Experience Platform Read

Dataset Name

String

Required. The name of the dataset from which you want to read the data. This is a suggestible field. Click  to view dataset suggestions that you can use.

This property is expression-enabled. For more information on the expression language, see Understanding Expressions in SnapLogic and Using Expressions. For information on Pipeline Parameters, see Pipeline Properties.

N/A

Adobe Demo 1 Dataset

Snap Execution

N/A

Specifies the execution type:

• Validate & Execute: Performs limited execution of the Snap (up to 50 records) during Pipeline validation; performs full execution of the Snap (unlimited records) during Pipeline execution.

• Execute only: Performs full execution of the Snap during Pipeline execution; does not execute the Snap during Pipeline validation.

• Disabled: Disables the Snap and, by extension, its downstream Snaps.

Validate

Missing property value

The snap settings are not correct.

You may see this error because you did not provide a mandatory value.

Check to ensure that all mandatory values are provided and valid.

Invalid Snap configuration

Target Dataset Name is null or missing.

This typically means that you did not specify the dataset in which the file must be read or that the dataset name specified does not exist in AEP.

Ensure that the property Dataset Name has a valid dataset name. Use the Suggestion button next to the Dataset Name field to select a valid dataset.

Unable to load the private key for the given alias

File not found on <your SnapLogic instance> at <account location>

This error appears when the account does not have valid values. Ensure that the keystore path, keystore passphrase, private key alias, and private key passphrase are correct. Also, you must upload the keystore in the Keystore Path that you specify.

Unable to obtain access token

This message appears when the endpoint account details are incorrect.

Check your Organization ID, Technical Account ID, Client ID, Client Secret Key details, and try again.