# Bug cloning Sales Orders

**URL:** <https://forum.manager.io/t/bug-cloning-sales-orders/26242>\
**Category:** Uncategorized\
**Created:** [January 10, 2020, 10:02pm UTC](https://forum.manager.io/t/bug-cloning-sales-orders/26242 "2020-01-10T22:02:40Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Tut](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.manager.io/tut/32/3286_2.png) [@Tut](https://forum.manager.io/u/Tut)\
**Post date:** [January 10, 2020, 11:07pm UTC](https://forum.manager.io/t/bug-cloning-sales-orders/26242/3 "2020-01-10T23:07:25Z")

</div>

What you describe is the result of a change introduced quite some time (many versions) ago in response to complaints from users. Cloning behavior was somewhat inconsistent across the program. Now, it has been standardized. When you clone a transaction, everything is cloned, making an exact copy of the source, with one exception. The exception is that the reference field follows whatever is set for that transaction type under Form Defaults. This is done to accommodate jurisdictions where sequential numbering is mandatory.

See [https://forum.manager.io/t/clone-transactions-and-reports/24890](https://forum.manager.io/t/clone-transactions-and-reports/24890).

As a result of the change, many users are happier. Businesses that send out similar sales invoices to multiple customers, for example, can clone one several times and change only the customer’s name, even if it takes them several days to prepare all the invoices.

---

_[View the full topic](https://forum.manager.io/t/bug-cloning-sales-orders/26242)._