Versions Compared

Old Version 19

changes.mady.by.user Subhajit Sengupta

Saved on

compared with

New Version 20

changes.mady.by.user Kalpana Malladi

Saved on

Key

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

On In this pagearticle

Table of Contents
maxLevel2
absoluteUrltrue

Overview

Use You can use this Snap to update Coupa resource records such as addresses, by using the relevant resource APIs. You can only use this Snap to select the resource whose records are to be updated; all record-related data must be passed through an upstream Snap such as the Mapper Snap.

Image RemovedImage Added

Note
titleAllowable Values

Some resource elements have a specific set of allowable values. An error is displayed if you provide any other value for such elements. Allowable values are mentioned in the Elements section in the resource's API documentation. 

For example, the change-type element in the Purchase Order resource accepts only change and revision.

...

  • Valid Coupa account with appropriate permissions.
  • Resource parameters compliant with the resource schema.

Limitations

None.

...

None.

Snap Input and Output

...

Snap Views

TypeFormatNumber of ViewsCompatible Upstream and Downstream SnapsDescription
Input Document
  • Min: 1
  • Max: 1
  • Mapper Snap
  • Copy Snap
The resource details as a JSON document.
OutputDocument
  • Min: 10
  • Max: 1
  • Document to Binary + File Writer

Details of the updated resource record. Level of detail varies according to the configuration of the Response Type field.

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 while running the Pipeline by choosing one of the following options from the When errors occur list under the Views tab. The available options are:

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

  • Discard Error Data and Continue: Ignores the error, discards that record, and continues with the rest of the 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

...

Info

  • Asterisk (*): Indicates a mandatory field.

  • Suggestion icon (Image Added): Indicates a list that is dynamically populated based on the configuration.

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

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

  • Remove icon (Image Added): Indicates that you can remove fields from the fieldset.


Field NameField TypeDescription

Label*


Default Value

Example Label

: Coupa Update
Example: Update Supplier Info


String
Required. Specifies
The name for the Snap. We recommend you update the Snap name, if there is more than one of the same Snap in your Pipeline.
N/AUpdate Supplier Info

Response Type

StringRequired. 

Response Type


Default Value: all
Example: shallow

Dropdown list

Specify the level of detail required in the Snap's output. You can configure this keeping in mind the available memory and likely processing time that it would take to execute this Snap. 

Available options are:

  • all: Output contains all details of the updated records.
  • none: No output.
  • limited: Output contains only the records' ID.
  • shallow: Output contains ID as well as the direct child attributes of each record.

See API Return Formats for more details

allshallowCoupa API NameStringN/A

API Path*


Default Value: N/A
Example: suppliers

String/Expression

The API name associated with the target resource. Select the target resource from the suggestions in the field. Suggestions vary based on the account.

Note

When updating specific resources, select the corresponding ID API and pass the resource ID as an upstream parameter. 

N/AsuppliersMark Exported


Snap executionN/ASpecifies the execution type

Mark Exported


Default Value: Not selected
Example: Selected

Checkbox

Select this checkbox to export the resource record after the update. This is only applicable to transactional resources such as contracts.

Note

Updating a resource record and marking a record as exported must not be done in the same request. If this field is selected, the record updates may be ignored. 

Not selectedN/A


Snap execution


Default Value: Execute only
Example: Validate & Execute

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.Execute onlyValidate & Execute

  • all Snaps that are downstream from it.

Examples

Fetching and Updating Inactive Records

This example demonstrates how you can to fetch one inactive Coupa supplier record and update one of its custom fields.

Image RemovedImage Added

Download the example Pipeline.

...

Attachments
patterns*.slp, *.zip

...

See AlsoRelated Links

...