> For the complete documentation index, see [llms.txt](https://help.adalo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.adalo.com/how-to/how-to-duplicate-records-for-repetitive-app-entries/how-to-edit-a-duplicated-record.md).
# How to Edit a Duplicated Record
Duplicating a record saves time, but the real advantage comes when you can immediately open and update the copy rather than hunting for it in a list. This walkthrough builds on the duplication setup and adds a second action that links directly to an edit screen, so users land on the new record the moment it's created.
***
### Set Up the Database
If you haven't already, create an **Activities** collection with the following fields:
* **Title** (text)
* **Notes** (text)
* **Type** (text)
***
### Create the Edit Screen
Add a new screen and name it **Edit Activity**. This is where users will land after tapping the copy button.
***
### Update the Duplicate Record
This ensures the copied data loads automatically so users can make changes right away rather than filling everything in from scratch.
**Action 1: Add Form Component to Update the Current Activity**
Set the fields to display from the newly duplicated record and allows your user to make any necessary changes.
**Action 2: Link to List of Records**
Add a Link action immediately after the Update action to
***
### Test the Flow
Preview your app and run through the full sequence:
1. Open an activity.
2. Tap the copy button.
3. Confirm the Edit Activity screen opens with the copied data pre-filled in the form.
4. Make an edit and save to verify the update sticks.
You can also check your database directly to confirm both the original and the edited copy exist as separate records.
***
### Learn More
* The newly created record is only available when actions run in sequence on the same button. Make sure the Link action comes directly after the Create action or the duplicated record won't pass correctly.
* You can extend this pattern to any collection, not just Activities. The same two-action approach works wherever duplication is useful.
* To give users a way to discard the copy, add a Delete action on the Edit screen tied to a cancel button, referencing the current record.
***
### Help
If you need additional help with this article, you can always ask in our[ community forum](https://forum.adalo.com/)! Be sure to paste the link to this article in your post as well!
Do you have a tutorial or help doc request? [Let us know!](https://forum.adalo.com/c/roadmap/10)
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://help.adalo.com/how-to/how-to-duplicate-records-for-repetitive-app-entries/how-to-edit-a-duplicated-record.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.