AvantGuard - Sage Intacct (Common Services) icon

AvantGuard - Sage Intacct (Common Services)

AvantGuard - Sage Intacct (Common Services)

Actions6

Overview

This node operation updates a core user view key within the "User Views" resource. It is designed to modify specific attributes of a user view by sending an update request with optional additional fields. This can be useful in scenarios where you need to programmatically adjust user interface configurations or permissions tied to user views in an application that supports such customization.

Practical examples include:

  • Changing the identifier or properties of a saved user view.
  • Updating metadata related to user views without manually accessing the backend.
  • Automating bulk updates to user views as part of a larger workflow.

Properties

Name Meaning
Additional Body Fields Optional fields to include in the update request body. Currently supports:
- Id: A string representing the identifier of the user view to update.

Output

The node outputs JSON data representing the response from the update operation on the user view. This typically includes confirmation of the updated fields, status messages, or the updated user view object itself depending on the API's response structure.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authentication to the external service managing user views.
  • The base URL for the API must be configured in the node credentials.
  • The node depends on an OpenAPI-based client library internally to build and send requests.

Troubleshooting

  • Missing or invalid Id: If the "Id" field is not provided or incorrect, the update will fail. Ensure the correct user view identifier is supplied.
  • Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
  • Network or API errors: Check connectivity and API endpoint availability.
  • Invalid additional fields: Only supported fields should be included in "Additional Body Fields"; unsupported fields may cause request rejection.

Links and References

  • Refer to the API documentation of the user view management system for detailed information on available fields and update semantics.
  • Consult n8n documentation on how to configure API key credentials and use collection-type input properties.

Discussion