# Not appending (1) on nested copied objects in folders

**URL:** <https://discourse.shapr3d.com/t/not-appending-1-on-nested-copied-objects-in-folders/24399>\
**Category:** Feature requests\
**Created:** [February 27, 2023, 12:08am UTC](https://discourse.shapr3d.com/t/not-appending-1-on-nested-copied-objects-in-folders/24399 "2023-02-27T00:08:58Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Curiobot](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.shapr3d.com/curiobot/32/8166_2.png) [@Curiobot](https://discourse.shapr3d.com/u/Curiobot)\
**Post date:** [February 27, 2023, 12:08am UTC](https://discourse.shapr3d.com/t/not-appending-1-on-nested-copied-objects-in-folders/24399/1 "2023-02-27T00:08:58Z")

</div>

When duplicating a folder, do _not_ append (1) or any other suffix to child objects of that folder.

**The problem that this feature will solve:**

Makes object hierarchy much cleaner. Encourages the use of duplicate pieces.

I often create one object, put it in a folder, then reuse it a lot - seeing a folder called **Hinge (6)** is fine, but **Hinge (6)** \> **Bracket (6)** \> **Leaf (6)** \> **Pin (6)** is irritating.

When it gets into an issue of modifying a nested object and re-duplicating it, it starts interfering with readability and name truncation. For example, splitting a body adds an asterisk - I’ve actually ended up with **Bracket (4) \* (1) \* \*\* (1)** before.

**Brief description of the outcomes that you expect from this feature:**

Helps keep complex projects organized, which is useful for professional use cases (especially when one project is shared between multiple users).

UX feature, for medium to power users.

**What can’t you achieve without this feature?**

This is not a workflow blocker. After a certain point I still have to work in Fusion 360, and this would help push that boundary out further.

This would make Shapr3D more appealing for larger, more complex projects. Makes Shapr more convincing sell to other CAD designers in-studio or prospective collaborators.

---

<div class="post-metadata">

**Author:** ![Stephen](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.shapr3d.com/stephen/32/16350_2.png) [@Stephen](https://discourse.shapr3d.com/u/Stephen)\
**Post date:** [February 27, 2023, 5:47pm UTC](https://discourse.shapr3d.com/t/not-appending-1-on-nested-copied-objects-in-folders/24399/2 "2023-02-27T17:47:42Z")

</div>

That’s a good suggestion 👍

---

<div class="post-metadata">

**Author:** ![mechstarpb](https://avatars.discourse-cdn.com/v4/letter/m/f4b2a3/32.png) [@mechstarpb](https://discourse.shapr3d.com/u/mechstarpb)\
**Post date:** [July 18, 2023, 4:48pm UTC](https://discourse.shapr3d.com/t/not-appending-1-on-nested-copied-objects-in-folders/24399/3 "2023-07-18T16:48:49Z")

</div>

Another +1 for this.  
Shapr team, please consider this.