Issue with Recipient Group Naming & API Usage
Issue:
Currently, when adding a new Recipient Group through the PandaDoc API (or manually) with the exact same name as an existing group, the existing group's members are overwritten or updated with the new group's members, instead of creating a distinct new group.
Impact:
This behavior causes significant issues and data inconsistencies, particularly when managing recipient groups programmatically via the API, as it leads to unintended changes in existing recipient lists.
Proposed Idea/Solution:
Please implement a system that ensures recipient groups with identical names are treated as separate and distinct entities. This could be achieved by:
Automatically appending a unique identifier (e.g., a number) to the group name if a duplicate is detected (e.g., "Group Name (1)", "Group Name (2)").
Allowing API users to explicitly create distinct groups even if names are identical.
This change would greatly improve data integrity and the reliability of recipient group management, especially for automated workflows.
