TwentyDEV icon

TwentyDEV

Consume the Twenty API
Join our community

Actions252

Overview

This node operation, Find View Filter Group Duplicates, is designed to identify duplicate view filter groups based on specified criteria. It allows users to query for duplicates by providing filtering data and optionally specifying particular IDs to check against. The node supports controlling the depth of related nested objects included in the response, enabling flexible retrieval of detailed or summarized information about the duplicates.

Common scenarios where this node is beneficial:

  • Cleaning up redundant or overlapping filter groups in a system to maintain data integrity.
  • Auditing and reporting on filter group usage and duplication within an application.
  • Automating maintenance tasks that require detection of duplicate configurations.

Practical example:
A user wants to find all duplicate view filter groups that match certain logical conditions (e.g., filters combined with AND operators) and retrieve related metadata up to one level deep. They provide the filter criteria as JSON data and specify the depth as 1 to get both the primary object and its directly related objects.

Properties

Name Meaning
Depth Determines the level of nested related objects to include in the response. Options are:
- 0: Returns only the primary object's information.
- 1: Returns the primary object along with its directly related objects.
- 2: Includes two levels of nesting for related objects.
Data JSON array defining the filter criteria for finding duplicates. Typically includes logical operators like "AND" to combine multiple conditions. This property controls which duplicates are matched based on their attributes.
Ids JSON array of IDs to specifically check for duplicates. Can be used to limit the search to certain view filter groups by their identifiers.

Output

The node outputs JSON data representing the found duplicate view filter groups. The structure includes the primary objects and, depending on the selected depth, their related nested objects. The output reflects the filtered results based on the input criteria.

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

Dependencies

  • Requires an API key credential to authenticate requests to the external Twenty API service.
  • The node uses the Twenty API base URL configured via credentials.
  • No additional environment variables are explicitly required beyond standard API authentication setup.

Troubleshooting

  • Invalid JSON in Data or Ids properties: Since these fields expect JSON input, malformed JSON will cause errors. Ensure valid JSON syntax when entering these values.
  • Authentication errors: If the API key or domain credentials are missing or incorrect, the node will fail to connect. Verify that the API key credential is properly configured.
  • Depth value out of range: Only 0, 1, or 2 are valid options for depth. Using other values may result in unexpected behavior or errors.
  • Empty or no duplicates found: If no duplicates match the criteria, the output will be empty. Adjust the filter criteria or IDs to broaden the search.

Links and References

Discussion