TwentyDEV icon

TwentyDEV

Consume the Twenty API
Join our community

Actions252

Overview

The "Find View Duplicates" operation in the Views resource is designed to identify duplicate views based on specified criteria. This node sends a request with detailed parameters describing how to detect duplicates, including which fields to consider and the depth of related objects to include in the response. It is useful in scenarios where you want to clean up or manage redundant views in a system, ensuring data consistency and avoiding clutter.

Practical examples:

  • Detecting duplicate dashboard views in a project management tool.
  • Finding repeated report configurations in an analytics platform.
  • Identifying redundant saved filters or search views in a CRM system.

Properties

Name Meaning
Depth Determines the level of nested related objects to include in the response:
- 0: Only the primary object's information.
- 1: Primary object plus directly related objects (no further nesting).
- 2: Primary object, its related objects, and their related objects.
Data JSON array specifying the criteria for finding duplicates. Each object can include properties like aggregation operations, keys, metadata IDs, and display names that define how duplicates are identified and presented.
Ids JSON array of IDs to limit the search scope to specific view identifiers. Can be used to target particular views when searching for duplicates.

Output

The node outputs JSON data representing the found duplicate views according to the specified criteria. The structure includes the primary view objects and, depending on the depth setting, their related nested objects. This output allows downstream nodes or workflows to process, analyze, or act upon the detected duplicates.

If binary data were involved (not indicated here), it would typically represent attachments or files related to the views, but this node focuses on JSON data.

Dependencies

  • Requires an API key credential to authenticate requests to the external Twenty API service.
  • Needs proper configuration of the API domain URL in the credentials.
  • Depends on the external Twenty API endpoint that supports the "Find View Duplicates" operation.

Troubleshooting

  • Common issues:

    • Invalid JSON format in the "Data" or "Ids" properties can cause request failures. Ensure these inputs are valid JSON arrays.
    • Incorrect or missing API credentials will result in authentication errors.
    • Setting an unsupported depth value outside 0, 1, or 2 may lead to unexpected responses or errors.

  • Error messages:

    • Authentication errors indicate problems with the API key or domain configuration; verify credentials.
    • Validation errors often point to malformed JSON input; validate JSON syntax before running.
    • API rate limits or network issues may cause timeouts or failed requests; check connectivity and API usage quotas.

Links and References

Discussion