Coupa Update
- Kalpana Malladi
- Mohammed Iqbal
- Gouri Bhagchandani
In this article
Overview
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.
Allowable 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.
If the change-type element's value is changed from change to revision, it cannot be reverted.
Prerequisites
- Valid Coupa account with appropriate permissions.
- Resource parameters compliant with the resource schema.
Limitations
None.
Snap Views
| Type | Format | Number of Views | Compatible Upstream and Downstream Snaps | Description |
|---|---|---|---|---|
| Input | Document |
|
| The resource details as a JSON document. |
| Output | Document |
|
| 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:
Learn more about Error handling in Pipelines. | |||
Snap Settings
Asterisk (*): Indicates a mandatory field.
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 static (if disabled). Learn more about Using Expressions in SnapLogic.Add icon (
): Indicates that you can add fields in the fieldset.Remove icon (
): Indicates that you can remove fields from the fieldset.
| Field Name | Field Type | Description |
|---|---|---|
Label* Default Value: Coupa Update | String | 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. |
Response Type Default Value: all | 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:
See API Return Formats for more details |
API Path* Default Value: N/A | 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. When updating specific resources, select the corresponding ID API and pass the resource ID as an upstream parameter. |
Mark Exported Default Value: Not selected | Checkbox | Select this checkbox to export the resource record after the update. This is only applicable to transactional resources such as contracts. 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. |
Snap execution Default Value: Execute only | Dropdown list | Select one of the three modes in which the Snap executes. Available options are:
|
Example
Fetching and Updating Inactive Records
This example demonstrates how to fetch one inactive Coupa supplier record and update one of its custom fields.
Download the example Pipeline.
The Coupa Read Snaps is configured as shown below:
Use Query Parameters field-set to filter the records. The Snap fetches all the supplier records, if this filter is not applied.
Based on this configuration, the Snap fetches the topmost inactive record for the supplier named Dell (USA).
In this example, we want to update one of the custom fields in the fetched record. To update a resource record, pass the record ID to the Coupa Update Snap. To do so, use the Mapper Snap connected to both Coupa Read and Coupa Update Snap. Additionally, provide the values to be updated. For example, custom-field-5 and John Doe in this case.
This Mapper Snap is configured as shown below:
Output from the Mapper Snap:
This data is passed into the Coupa Update Snap which is configured as shown below:
The response type is limited; therefore, only the updated data is shown in the output:
Downloads
Important steps to successfully reuse Pipelines
- Download and import the pipeline into the SnapLogic application.
- Configure Snap accounts as applicable.
- Provide pipeline parameters as applicable.
Snap Pack History
Related Links
Have feedback? Email documentation@snaplogic.com | Ask a question in the SnapLogic Community
© 2017-2024 SnapLogic, Inc.