> For the complete documentation index, see [llms.txt](https://docs.inogic.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inogic.com/click2clone/configuration/cloning-a-record/setup-fields-to-copy.md).

# Set up fields to copy

To set up fields to copy, follow the steps given below:

* Go to **Attribute/Relationship** **to Clone** section --> **Attributes** -->Select the **fields** from the attributes list that you would like to copy --> Click on **Save.**

![](/files/-M6X-DdaT1kgYLOBvRnJ)

* If the attribute list does not populate/load or remains blank then refresh the grid by clicking **'Refresh'** and proceed with selection of fields.

![](/files/-M6X-xJ8jHGGdgRmocFt)

{% hint style="info" %}
**Note:**&#x20;

**In CRM, when you create a new Work Order, the unique work order number will be auto-populated. This ensures that no two work orders have the same number.**

**So, during the cloning process of the Work Order entity, choosing the "msdyn\_name" field from the attribute list results in the creation of a cloned copy with the same work order number as the original, and hence it gives the error “The work order number must be unique.”**

**Furthermore, the "msdyn\_name" field depends on the "msdyn\_autonumbering" field to generate a work order number. Therefore, it is essential to uncheck this field as well.**

**So, while cloning the Work Order entity, if these two fields, i.e., "msdyn\_name" and "msdyn\_autonumbering," are not selected, then a cloned copy of the work order will be generated with a new work order number.**

**Apart from the above-mentioned two fields, the user can select other fields from the attribute list for a new cloned copy of the work order.**

{% endhint %}

{% hint style="success" %}
For further queries, reach out to us at <crm@inogic.com>
{% endhint %}


---

# 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://docs.inogic.com/click2clone/configuration/cloning-a-record/setup-fields-to-copy.md?ask=<question>&goal=<endgoal>
```

`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.
