Duplicate record functionnality

[n2ojim]

Scope & Context

We want to enable users to easily duplicate one or multiple records directly from the interface, without having to use the API, workflows, or manually recreate them. This feature should be accessible through keyboard shortcuts and the command menu to provide a seamless and quick user experience.

Current behavior

Currently, there is no native way to duplicate a record in the UI. Users have to either manually create a new record and copy-paste all the fields from the original one, use the API, or build a specific workflow (e.g., using "Upsert").
In the command menu (opened with Ctrl+K or Cmd+K), options exist for editing the page layout or deleting a record, but not for duplicating.

Expected behavior

Users should be able to duplicate a selected record (or multiple selected records in a view) using the standard keyboard shortcuts Ctrl+C (or Cmd+C) to copy, and Ctrl+V (or Cmd+V) to paste and create the duplicate(s).
Additionally, a "Duplicate" action should be available in the command menu (Ctrl+K / Cmd+K), ideally positioned right near or under the "Delete" option for easy access.
When a record is duplicated, the new record should copy all standard and custom field values from the original, except for unique identifiers (like system IDs) which should be newly generated.

Technical inputs

• Add event listeners for Ctrl+C/Cmd+C and Ctrl+V/Cmd+V at the view/table level and record page level when a record is focused/selected.
• Update the Command Menu (Ctrl+K) component to include a new "Duplicate record" MenuItem.
• Create a handler function that fetches the selected record(s) data (excluding system-generated immutable fields like id, createdAt, etc.) and triggers a create mutation with the duplicated data.
• Ensure validation rules (like unique constraints on specific fields) are handled gracefully (e.g., appending "- Copy" to a unique text field or prompting the user).
• Display a success toast notification once the duplicated record(s) are created, potentially with a link to view the new record.

[FelixMalfait]

For this one what is tricky is to handle the relationships / know which child to copy. Copying the parent is easy, but then do you link it to the same child? do you duplicate some of the childs? the parents? etc.

[benweissbehavehealth]

this is a very good point, there is some complexity there in the child records for sure. I don't have a great answer, but I know you all would come up with something good!

Maybe just a choice:

1. duplicate all child records
   2a. don't duplicate all child records and associate duplicate record with the same child records
   2b. don't duplicate all child records and don't associate duplicate record with the same child records

[n2ojim]

I would go for a relation detection and a modal choice when the record contains relations :

• Keep the same children relations
• Keep the children relations empty

Advanced suggestions:

• Choose what to do individually
• Make 2 different button shortcuts : Duplicate selected records (keep relations) / Duplicate records (empty relations)

I think this duplicate function can be really useful for some industries.