Actions6
- Allowed Operations Actions
- Composite Requests Actions
- Models Actions
- Query Actions
- User Views Actions
Overview
The "Create Core User View" operation under the "User Views" resource allows users to create a customized system view within an application, typically for managing or displaying user-related data. This node is useful when you want to define specific views that filter, sort, and present data according to particular criteria, making it easier to access relevant information quickly.
Practical examples include:
- Creating a view that shows only active vendors with outstanding balances above a certain threshold.
- Defining a public or private view tailored to specific user roles or departments.
- Setting up complex queries with filters and ordering to generate reports or dashboards dynamically.
This operation supports detailed customization of the view's metadata, query parameters, ownership, and status, enabling flexible and powerful data presentation.
Properties
| Name | Meaning |
|---|---|
| Name | The name of the user view. |
| Additional Body Fields | Optional additional fields to customize the user view further. These include: - Key: Unique key identifying the view in URLs or JSON bodies. - Id: Unique ID, same as key. - Href: URL endpoint of the view. - Status: Object status; can be "Active" or "Inactive". - Description: Description of the view. - Object: The object queried to create the view. - Category: Category of the view. - View Version: Version identifier. - Is Public: Boolean indicating if the view is shared publicly or private. - Context: Context of the view. - Query: JSON defining the query request including object, fields, filters, filter expressions, order, pagination, etc. - Metadata: JSON controlling how the view is presented in the UI. - Owner: JSON describing the user who created the view. - Audit: JSON containing audit info like 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 data returned by the API, such as unique identifiers or confirmation details.
If the node supports binary data output (not indicated here), it would typically represent attachments or files related to the user view, but this operation primarily deals with JSON data.
Dependencies
- Requires an API key credential for authentication to the backend service managing user views.
- Needs proper configuration of the base URL for the API endpoint.
- Depends on the external Sage Intacct API or a similar backend service that handles user view creation.
Troubleshooting
- Missing Required Fields: If the "Name" property is not provided, the node will likely throw an error because it is required.
- Invalid JSON in Query or Metadata: Providing malformed JSON in the "Query", "Metadata", "Owner", or "Audit" fields may cause parsing errors. Ensure JSON syntax is correct.
- API Authentication Errors: Incorrect or missing API credentials will result in authentication failures.
- Status Field Issues: Using invalid values for the "Status" field other than "active" or "inactive" may cause rejection by the API.
- Permission Denied: Attempting to create a view without sufficient permissions or with an invalid owner may lead to authorization errors.
To resolve these issues:
- Double-check required fields and their formats.
- Validate JSON inputs using online tools before submission.
- Verify API credentials and permissions.
- Use only supported option values for enumerated fields.