Versions Compared

Old Version 2

changes.mady.by.user Kalpana Malladi

Saved on

compared with

New Version Current

changes.mady.by.user Gouri Bhagchandani

Saved on

Key

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

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

In this article

...

Overview

...

Table of Contents

...

...

...

minLevel1
maxLevel3

Overview

You can use this Snap to update a data object in the Exact Online instance. Image Removed

...

Prerequisites

A valid OAuth 2.0 account that supports Exact Online instance, with the appropriate access permissions. See Exact Online OAuth 2.0 Account.

Support for Ultra Pipelines

Works in Ultra Pipelines. 

...

See Snap Support for Ultra Pipelines.

Limitations and Known Issues

None

Snap

...

Input/Output

...

Views

View Type

View Format

Number of Views

Examples of Upstream and Downstream Snaps

Description

Input 

Document

  • Min: 1

  • Max: 1

  • Mapper Snap

  • Copy Snap

  • JSON Parser

Each input document contains data that must be updated and written into the

SAP S/4HANA On-Premise

Exact Online Update on-premise instance for the selected entity.

Output

Document

  • Min: 0

  • Max: 1

  • Mapper Snap

  • Copy Snap

  • JSON Formatter

Each document contains the response of the update operation.

Error

Document

  • Min: 1

  • Max: 1

N/A

The error view contains error, reason, resolution and stack trace. For more information, see Handling Errors with an Error Pipeline.

Snap Settings

...

Field names marked with an asterisk ( * ) are mandatory.

Field Name

Data

Field Type

Description

Default Value

Example 

Label*

String

Required. The

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

Default Value: N/A

SAP S/4HANA

Example: Exact Online Update

Version*

String

Required. The version of

Specify the version of the Exact Online API.

Default Value: v1
Example: v1

Division*

String

Required. Unique

/Expression/Suggestion

Specify an unique ID of the Exact Online Division. The Exact Online

Division (can be retrieved with a REST call https://start.exactonline.nl

REST API resource URIs require a Division parameter. This parameter identifies the division that is accessed. The specific division can be found by calling /api/v1/current/Me. For example: /api/v1/current/Me?

).

$select=CurrentDivision

Default Value: N/A
Example: 1234567

API object*

String/Expression/Suggestion

Required.

Select the API that you want to access in the Exact Online instance. This drop-down list contains supported services available for the Exact Online instance.

Default Value: N/A
Example: CRM

Endpoint*

String

Required. Select

/Expression/Suggestion

Select an Exact Online Endpoints to be specified and connected for each of the API objects.

Default Value: N/A
Example: Accounts

ID

String

Unique

/Expression/Suggestion

Specify a unique Exact Online identifier (

Guid

GUID) of the record to be updated.

Default Value: N/A
Example: a8ecb3d6-6632-11eb-ae93-0242ac130002

Connection details

Use this section of Snap Settings to specify the connectivity parameters: timeout, retry count and retry interval.  This field set comprises the following fields:

  • Connection timeout

  • Maximum request attempts

  • RetryInterval

    •  

     

     

     

     

     

    • Retry Interval

    Connection timeout*

    Integer

    Required.

    Enter, in seconds, the duration for which Snap must try to establish a connection with the Exact Online instance. If the connection cannot be established within this duration, the Snap times out writes the event to the log and waits until the specified 

    RetryInterval

    Retry Interval before attempting to reconnect.

    Default Value: 300
    Example: 120

    Maximum request attempts*

    Integer

    Required.

    Specify

    an integer value to set

    the maximum number of reconnection attempts that the Snap must perform, in case of connection failure or timeout.

    Default Value: 0
    Example: 5

    RetryInterval

    Retry Interval*

    Integer

    Required. Enter, in seconds,

    Specify the duration for which the Snap must wait between two reconnection attempts until the number of retries is reached.

    Default Value: 0
    Example:10

    Snap Execution

    String

    Indicates how the Snap must be executed

    Dropdown list

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

    • Validate & Execute: Performs limited execution of the Snap

    (up to 50 records)

    • , and generates a data preview during Pipeline validation

    ;

    • . Subsequently, performs full execution of the Snap (unlimited records) during Pipeline

    execution

    • runtime.

    • Execute only: Performs full execution of the Snap during Pipeline execution

    ; does not execute the Snap during Pipeline validation. ·      

    • without generating preview data.

    • Disabled: Disables the Snap and

    , by extension, its downstream Snaps.

    • all Snaps that are downstream from it.

    Default Value: Execute only
    Example: Validate & Execute 

    Troubleshooting

    Error

    Reason

    Resolution

    API object is not existing.

    The entered API object is not found for the Exact Online API.

    Please search

    Search and select an API object from the dropdown list.

    The endpoint is not existing.

    The entered Endpoint is not found for the selected API object in the server.

    Please search

    Search and select the Endpoint from the dropdown list.

    Additional Information

    Here is some information to assist you while using the Exact Online Update Snap.

    ...

    The Exact Online Update Snap supports the following:

    • PUT operation to Update data in the Exact Online instance.

    • Display of

      Displays only the update-compatible input parameter set from the upstream input Snap.

    • Dynamic loading of API metadata with a Parent-child dependency structure. This means that you can:

      • Select an API object from the API Object field to view only entities that are related to the API object and support PUT queries (update operations).

      • And then, select an entity to view and specify values for only update-compatible parameters for input schema.

    Input schema

    The input schema for Exact Online Update Snap:  Image Removed

    • Use the Payload schema for Exact Online Update Snap to define the input payload for an API call. This dynamically loads and represents all the parameters that you need for creating the data object (payload). 

      • If the upstream Snap can display the entire input schema like Mapper Snap, always select the Payload object in the schema to define your input payload in that Snap.

      • If your input payload is a JSON object, ensure that the text Payload is included as the key in the parent of your input.

    Schema settings

    Parameter Name

    Data Type

    Description

    Default Value

    Example 

    Payload

    Object

    Specify the input data parameters for the selected entities.

    N/A

    N/A

    ...

    Example

    ...

    Updating account details from Exact Online Instance CRM service

    This Pipeline example demonstrates using an Exact Online Update Snap how to update account details in the Exact Online instance CRM service. The This example assumes that you have configured and authorized a valid Exact Online Account (see . See Configuring Exact Online Accounts (file:////wiki/spaces/SD/pages/......)). Image Removed Download this Pipeline    The following settings are defined for the Exact Online Update Snap to update account details from the Exact Online instance Account.

    ...

    We configure the Exact Online Update Snap with the following settings to retrieve Accounts data from the Exact Online instance CRM service it accesses.

    • API object: CRM

    • Endpoint: Accounts

    ...

    After successful validation, we can view the following output preview, showing showing the query results . Image Removed A in the Snap’s preview 

    ...

    We connect the JSON Formatter Snap is connected to the SAP S/4HANA Update upstream Snap to read and format its the output data into standard JSON format. A Next, we connect the File Writer Snap is connected to the JSON Formatter Snap to save / write the JSON -formatted data into a file. Image Removed Image Removed Output

    ...

    To view the output JSON file, you must SSH to the target directory and open the newly-created JSON file. The preview of the output JSON file can be seen below: Image Removed

    ...

    Download this Pipeline.

    Downloads

    Info

    Important Steps to Successfully Reuse Pipelines

    1. Download and import the Pipeline into SnapLogic.

    2. Configure Snap accounts as applicable.

    3. Provide Pipeline parameters as applicable.

    ...

    Attachments

    ...

    File

    ...

    Modified

    ...

    Labels

    ...

    Snap Pack History

    Image Removed Click here to expand...

    ...

    Release

    ...

    Snap Pack Version 

    ...

    Type

    ...

    Updates

    ...

     

    ...

     

    ...

     

    See Also

    ...

    patterns*.slp, *.zip

    Snap Pack History

    Expand

    Insert excerpt
    Exact Online Snap Pack
    Exact Online Snap Pack
    nameExact Online Snap Pack History
    nopaneltrue

    ...

    Related Content