TwentyDEV icon

TwentyDEV

Consume the Twenty API
Join our community

Actions252

Overview

The "Find View Group Duplicates" operation in the "View Groups" resource is designed to identify duplicate view groups based on specified criteria. This node is useful when you want to detect and handle redundant or overlapping view groups within your data, which can help maintain data integrity and optimize data management.

Typical use cases include:

  • Cleaning up duplicate entries in a database of view groups.
  • Automating the detection of similar or identical view groups for reporting or merging.
  • Integrating with systems where view group uniqueness is critical.

For example, if you have multiple view groups that may share common metadata fields, this operation can find duplicates by comparing those fields according to the provided parameters.

Properties

Name Meaning
Depth Determines how deeply nested related objects are included in the response:
- 0: Only the primary object's information.
- 1: Primary object plus its 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 item typically includes identifiers such as fieldMetadataId to define which fields to consider when detecting duplicates.
Ids JSON array of IDs to limit the search scope to specific view groups. Can be used to target particular view groups for duplicate detection.

Output

The node outputs JSON data representing the found duplicate view groups according to the specified criteria. The structure includes the primary view group objects along with related objects depending on the selected depth level.

If binary data were involved, it would typically represent attachments or files related to the view groups, but this operation focuses on JSON data output only.

Dependencies

  • Requires an API key credential to authenticate requests against the Twenty API service.
  • The node uses the Twenty API base URL configured via credentials.
  • No additional external dependencies beyond the API access are required.

Troubleshooting

  • Invalid JSON in Data or Ids properties: Since these properties expect JSON input, malformed JSON will cause errors. Ensure valid JSON syntax.
  • Authentication errors: If the API key or domain is misconfigured, authentication will fail. Verify credentials are correctly set.
  • Empty results: If no duplicates are found, check that the data criteria and ids filters are correctly specified and match existing view groups.
  • Depth parameter misuse: Setting depth too high might return large payloads; adjust according to needs.

Links and References

Discussion