Anaplan Write
Overview
Write-type Snap-
Works in Ultra Pipelines
You can use this Snap to import Anaplan server file to Anaplan model.
Prerequisites
None.
Limitations and Known Issues
None.
Snap Views
| View | Description | Examples of Upstream and Downstream Snaps |
|---|---|---|
| Input | Document containing same type of records. | |
| Output | Document containing the Date and time finished, Failed or non-failed message with any details provided by Anaplan server. | |
| 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. The available options are:
Learn more about Error handling in Pipelines. |
|
Snap Settings
-
Suggestion icon (
):
Indicates a list that is dynamically populated based on the configuration.
-
Expression icon (
):
Indicates whether the value is an expression (if enabled) or a static value (if disabled).
Learn more about Using Expressions in SnapLogic.
-
Add icon (
):
Indicates that you can add fields in the field set.
-
Remove icon (
):
Indicates that you can remove fields from the field set.
| Field / Field Set | Type | Description |
|---|---|---|
| Label | String | Required. Specify a unique name for the Snap. Modify this to be more appropriate, especially if there are more than one of the same Snap in the pipeline. |
| Workspace | String/Expression/Suggestion |
Required.
Specify the workspace that contains the target model.
Default: N/A Example: snaplogic |
| Model | String/Expression/Suggestion |
Required.
Specify the model on which you want the Snap to operate.
Default: N/A Example: snap test |
| Import name | Checkbox |
Required.
Specify the name of the import to run.
Default: N/A Example: customerl.csv |
| Server Filename | String/Expression/Suggestion |
Required.
Specify the file name for an Anaplan server file.
Default: N/A Example: customerl.csv |
| Overwrite File | Checkbox |
Select this checkbox to overwrite the Anaplan server file.
If deselected, an error is displayed if the file with the same name already exists.
Default status: Selected |
| Upload Only | Checkbox |
Select this checkbox to upload the server file and not run an import job.
Default status: Deselected |
| Override server settings | Checkbox/Expression |
Select this checkbox to override the settings saved on Anaplan's server for Separator, Text Delimiter, Header Row, and First Data Row.
Default status: Deselected |
| Separator | Dropdown list |
Required.
Select the column separator for the Snap to use.
The available options are:
Note:
Default value: TAB Example: COMMA |
| Text Delimiter | Dropdown list |
Required.
Select the the text delimiter for the Snap to use. The available options are:
Note: Note that the Anaplan server might ignore this setting and try to auto detect.
Default value: DOUBLE_QUOTE Example: NONE |
| Retry limit | Integer/Expression |
Required.
Specify the maximum number of connection retry attempts in case of a connection failure.
If the retry attempts exceed the configured value, the pipeline execution fails and an error message appears.
Default value: 3 Example: 8 |
| Retry interval | Integer/Expression |
Required.
Specify the minimum retry time interval in seconds.
Enter the time interval for the Snap to retry a connection request after a failed connection.
The time increases exponentially between failures.
For example, if the timeout is set to 3 seconds, the first timeout is at 3, the second is at 4.5 etc.
Default value: 3 Example: 6 |
| HTTP timeout | Integer/Expression |
Required.
Specify the connection timeout value in seconds.
In case of a connection failure, the Snap aborts the pipeline execution.
For example, if the HTTP timeout is set to 30 seconds, and the Snap fails to establish a connection until 30 seconds, the pipeline logs a timeout exception and aborts execution.
Default value: 60 Example: 30 |
| Snap Execution | Dropdown list | Select one of the three modes in which the Snap executes.
Available options are:
|
Temporary Files
During execution, data processing on Snaplex nodes occurs principally in-memory as streaming and is unencrypted. When processing larger datasets that exceed the available compute memory, the Snap writes unencrypted Pipeline data to local storage to optimize the performance. These temporary files are deleted when the Snap/Pipeline execution completes. You can configure the temporary data's location in the Global properties table of the Snaplex's node properties, which can also help avoid Pipeline errors due to the unavailability of space. For more information, see Temporary Folder in Configuration Options.