# Clone of model node can change the original model node

**URL:** <https://discourse.slicer.org/t/clone-of-model-node-can-change-the-original-model-node/14521>\
**Category:** Support\
**Tags:** subject-hierarchy\
**Created:** [November 10, 2020, 4:16pm UTC](https://discourse.slicer.org/t/clone-of-model-node-can-change-the-original-model-node/14521 "2020-11-10T16:16:17Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ungi](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/ungi/32/78573_2.png) [@ungi](https://discourse.slicer.org/u/ungi)\
**Post date:** [November 10, 2020, 4:16pm UTC](https://discourse.slicer.org/t/clone-of-model-node-can-change-the-original-model-node/14521/1 "2020-11-10T16:16:17Z")

</div>

Tested on Windows with latest stable (4.11.20200930) version.  
How to reproduce:

1. Load or create a surface model node.
2. Clone it in the Data module
3. Create a transform node for the clone (model copy) and move it somewhere else
4. Harden the transform on the clone.  
At this point I would expect the original surface model node to not change. However, at the point of hardening the transform, both models go to the new transformed position. So I think the poly data is not really duplicated when cloning the model node.  
I think this is bug, the original node should not depend on changes made in the cloned node.

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [November 10, 2020, 7:22pm UTC](https://discourse.slicer.org/t/clone-of-model-node-can-change-the-original-model-node/14521/2 "2020-11-10T19:22:40Z")

</div>

Thanks for reporting this, I’ve fixed this [here](https://github.com/Slicer/Slicer/commit/6f3975bb4e6913bbff553733f047010a298bb3c3), will be available in tomorrow’s Preview Release.