Versions Compared

Old Version 3

changes.mady.by.user Shilpa

Saved on

compared with

New Version 4

changes.mady.by.user Shilpa

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

You can use this Snap to read data from upstream Snaps and prepare them for writing into Adobe Enterprise Platform (AEP) as JSON or Parquet files.

...

Snap Type

The Adobe Experience Platform File Generator Snap is a read Snap that reads data from the upstream Snaps.

Prerequisites

The schema that you want to use with this Snap should exist in the Adobe Experience Platform. If you do not have the schema ready, create it using the Adobe Experience Platform user interface before using this Snap.

Limitations and Known Issues

While When the Schema Name, Dataset Name, and Connectors Object Name fields are expression enabled, their purpose is to read Pipeline parameter values. This Snap does not read values from upstream Snaps. You can , however, add this Snap in to the Pipelines with other Snaps to execute them in a sequence.

Snap

...

Input/Output

...

Views

Type

Format

Number of Views

Compatible

Examples of Upstream and Downstream Snaps

Description

Input 

Document

  • Min: 1

  • Max: 1

  • Mapper Snap

  • Binary to Document Snap

  • Sort Snap

Each input document contains documents that must be prepared for writing to Adobe Experience Platform.

Output

Document

  • Min: 1

  • Max: 1

  • Mapper Snap

  • Join Snap

  • Union Snap

Each output document lists out the absolute path to the reformatted output file.

Error

Error handling is a generic way to handle errors without losing data or failing the Snap execution. You can handle the errors that the Snap might encounter when running the Pipeline by choosing one of the following options from the When errors occur list under the Views tab:

  • Stop Pipeline Execution: Stops the current Pipeline execution if the Snap encounters an error.

  • Discard Error Data and Continue: Ignores the error, discards that record, and continues with the remaining records.

  • Route Error Data to Error View: Routes the error data to an error view without stopping the Snap execution.

Learn more about Error handling in Pipelines.

Snap Settings

...

Parameter Name

...

Data Type

...

Description

...

Default Value

...

Example 

...

Label

...

String

...

Info

  • Asterisk ( * ): Indicates a mandatory field.

  • Suggestion icon ((blue star)): Indicates a dynamically populated list based on the configuration.

  • Expression icon ((blue star) ): Indicates the value is an expression (if enabled) or a static value (if disabled). Learn more about Using Expressions in SnapLogic.

  • Add icon ( (blue star) ): Indicates that you can add fields in the fieldset.

  • Remove icon ( (blue star)): Indicates that you can remove fields from the fields set.

  • The upload icon ((blue star) ): Indicates that you can upload files.

Field Name

Field Type

Description

Label*

 

Default Value: Adobe Experience Platform File Generator
Example: Read and Reformat Documents from S3

String

The name for the Snap. Modify this to be more specific, especially if there is more than one of the same Snap in the Pipeline.

Adobe Experience Platform File Generator

Read and Reformat Documents from S3

Schema Name

String

Required. The

Schema Name*

 

Default Value: NA
Example: Snaplogic Demo Experience Event Schema

String

The name of the schema to be used to create the output Parquet or JSON file. This schema should already have been created in

AEP

the Adobe Experience Platform.

This Snap reads Pipeline parameters

,

but not values from upstream Snaps.

 You can, however,

Schema Type

String

Required. The schema type that

 However, you can add this Snap in Pipelines with other Snaps to execute them in a sequence.

Schema Type

 

N/A

Snaplogic Demo Experience Event Schema

Default Value: Parquet
Example: JSON

Dropdown list

Select the schema type you want to use to create the

output

file

. Click to select from the following options

that must be written. The options available are:

  • Parquet

  • JSON

Parquet

JSON

Snap Execution

String

Snap Execution

Default Value: Execute only
Example: Validate & Execute

Dropdown list

Select one of the following 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

  • complete execution of the Snap (unlimited records) during Pipeline runtime.

  • Execute only: Performs

full

  • complete execution of the Snap during Pipeline execution without generating preview data.

  • Disabled: Disables the Snap and all Snaps that are downstream from it.

Execute only

Validate and Execute

Troubleshooting

Error

Reason

Resolution

Invalid Snap configuration

Property Schema Name is null or missing

.This typically means that either you did not specify the schema that you want to use or misspelled the schema name.

Provide a valid schema name.

Unable to load the private key for the given alias

Keystore file

File not found

at the given keystore path.

on <your SnapLogic instance> at <account location>

This error appears when the account doesn't have valid values. Ensure that the

keystore

Keystore path,

keystore

Keystore passphrase, private key alias, and private key passphrase are correct. Also, you must upload the

keystore

Keystore in the Keystore Path that you specify.

Unable to obtain the access token

This message appears when the endpoint account details are incorrect.

Check your Organization ID, Technical Account ID, Client ID,

 Client

 and Client Secret Key details and

try again

retry.