# \[Bug-12661\] Duplicate Property Key Corrupts Original Property Value

**URL:** <https://forum.inductiveautomation.com/t/bug-12661-duplicate-property-key-corrupts-original-property-value/22430>\
**Category:** Ignition Early Access\
**Created:** [February 7, 2019, 2:03pm UTC](https://forum.inductiveautomation.com/t/bug-12661-duplicate-property-key-corrupts-original-property-value/22430 "2019-02-07T14:03:58Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![cmallonee](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cmallonee/32/6416_2.png) [@cmallonee](https://forum.inductiveautomation.com/u/cmallonee)\
**Post date:** [February 7, 2019, 10:30pm UTC](https://forum.inductiveautomation.com/t/bug-12661-duplicate-property-key-corrupts-original-property-value/22430/3 "2019-02-07T22:30:55Z")

</div>

I’ve opened an internal ticket for this one. The fix to defer updates is actually doing what it is supposed to - this is just a side-effect; originally, a key was written to the View after each key press (which is why you had an instant collision), which no longer happens. The fix for the key deferment did not include any acceptance around preventing name collisions.

---

_[View the full topic](https://forum.inductiveautomation.com/t/bug-12661-duplicate-property-key-corrupts-original-property-value/22430)._