# Duplicate Submissions
On the web, as on mobile, it is possible to duplicate submissions individually or in bulk, except for submissions under a workflow that are not in the initial state.
## Configure data to duplicate
By default, when a submission is duplicated, all of the information it contains is copied. From the form, it is possible to define the values of the fields to duplicate in a submissions. This is configured in the advanced settings of your form:
## From the web
### In bulk
From the table view, after selecting one or more cards, click on **Actions** then **Duplicate**:
### Single
From the table view, open one submission and click on **Actions** then **Duplicate:**
You will be redirected to a view allowing you to modify the duplicate submission before saving it. This way, you can duplicate a submission that is not in the initial workflow state. In return, for technical reasons, sub-content relation fields (see below) are not duplicated.
## From mobile
{% tabs %}
{% tab title="Android" %}
### In bulk
* Go to the "My Submissions" view
* Long-press a submission row to enter selection mode
* Tap the duplication icon in the top menu
* Confirm
* The submissions are duplicated as drafts
{% endtab %}
{% tab title="iOS" %}
### Single
* Go to the "My Submissions" view
* Swipe left on a submission row to reveal the action menu
* Select **Duplicate**
* The duplicate submission is created as a draft
{% endtab %}
{% endtabs %}
## Special case of relation
When duplicating a submission, if a relationship field needs to be copied, we use the relationship parameters to know what to do.
Also be careful not to put the same system name on your relationship element fields (and formulas based on a child field) so that the form is duplicated.
**Relationship of the "Plan" type**
When duplicating a submission that contains a relation of the "Plan" type, the relation field will be emptied.
### Duplication behavior
When setting up your relation field, you will see an option related to duplication
This allows you to choose how the relation field should be duplicated, amongst the 2 below options
* **Duplicate child submissions:** The child submissions that were in the relation field you are copying from will be duplicated. Meaning new entries will also be created for the child form
* **Link to existing child submissions**: The copied submission will have a link to the existing child submissions you are copying from. Meaning no new entries will be created for the child form. This is best used in relations of "Selection" type, when the child form you are selecting submissions from is acting as a "database". Ex: If you have a main form for *transactions*, and a child form for products, when duplicating the transaction you don't want to duplicate the products, as it will lead to duplicates in your *product* form
---
# Agent Instructions: 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:
```
GET https://www.center.daxium-air.com/user-documentation/use/views/actions-from-views/duplication.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.