AvantGuard - Sage Intacct (Common Services)

Actions6

Allowed Operations Actions
- List Allowed Operations
Composite Requests Actions
- Post Services Composite
Models Actions
- Get Services Model
Query Actions
- Post Services Query
User Views Actions
- Create Core User View
- Update Core User View Key

Overview

The "Create Core User View" operation under the "User Views" resource allows users to create a customized system view for core user data within an application, likely related to Sage Intacct. This node is useful when you want to define and save specific views that filter, sort, and display user-related data according to custom criteria.

Typical use cases include:

Creating personalized dashboards or reports by defining which fields to show and how to filter records.
Sharing views publicly or keeping them private to control access.
Automating the creation of user views as part of a larger workflow to standardize data presentation.

For example, you might create a user view that shows all active vendors with a credit limit above a certain threshold, sorted by their last payment date.

Properties

Name	Meaning
Name	The name of the user view.
Additional Body Fields	Optional additional parameters to customize the user view:
- Key	System-assigned unique key identifying the user view in URLs or JSON bodies.
- Id	Unique ID of the view, same as `key`.
- Href	URL endpoint of the user view.
- Status	Status of the object; can be Active (fully functional) or Inactive (hidden and unusable).
- Description	A textual description of the view.
- Object	The object queried to create the system view (e.g., accounts-payable/vendor).
- Category	Category classification of the view.
- View Version	Version identifier of the view.
- Is Public	Boolean flag indicating if the view is shared with everyone who has access (`true`) or private to the owner (`false`).
- Context	Contextual information about the view.
- Query	JSON object defining the query request, including:
	• Object to query
	• Fields to retrieve
	• Filters with conditions (e.g., equals, greater than, contains)
	• Filter expression logic
	• Filter parameters such as date, case sensitivity, hierarchy inclusion, privacy
	• Order by fields and directions
	• Pagination start and size
- Metadata	JSON metadata controlling how the view is presented in the UI, e.g., column configurations.
- Owner	JSON describing the user who created the view.
- Audit	JSON audit information including creation and modification timestamps and user IDs.

Output

The node outputs a JSON object representing the newly created user view. This output includes all properties sent in the request along with any additional server-generated fields such as unique identifiers or status confirmations.

No binary data output is involved.

Dependencies

Requires an API key credential for authentication to the Sage Intacct API or equivalent service.
The base URL for the API must be configured in the node credentials.
The node uses JSON-formatted requests and expects JSON responses from the API.

Troubleshooting

Missing Required Fields: If the required "Name" property is not provided, the API will reject the request. Ensure all mandatory fields are filled.
Invalid JSON in Query or Metadata: The "Query", "Metadata", "Owner", and "Audit" fields expect valid JSON strings. Malformed JSON will cause errors.
Permission Issues: Setting "Is Public" to true requires appropriate permissions; otherwise, the API may return authorization errors.
Status Errors: Using invalid values for "Status" other than "active" or "inactive" will result in validation errors.
API Connectivity: Ensure the API base URL and credentials are correctly set up; network or authentication failures will prevent successful execution.