# \[IGN-1660\]PSA - Assigning values to a property in a script may drive you nuts

**URL:** <https://forum.inductiveautomation.com/t/ign-1660-psa-assigning-values-to-a-property-in-a-script-may-drive-you-nuts/76192>\
**Category:** Ignition\
**Tags:** perspective, scripting, ignition81\
**Created:** [July 11, 2023, 2:29pm UTC](https://forum.inductiveautomation.com/t/ign-1660-psa-assigning-values-to-a-property-in-a-script-may-drive-you-nuts/76192 "2023-07-11T14:29:25Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [July 11, 2023, 2:42pm UTC](https://forum.inductiveautomation.com/t/ign-1660-psa-assigning-values-to-a-property-in-a-script-may-drive-you-nuts/76192/4 "2023-07-11T14:42:52Z")

</div>

> [@pascal.fragnoud](#):
>
> `data = self.custom.data`

Among other things, basically, don't do this. You're capturing the 'property tree' wrapper housed at `self.custom.data` in your script. Mutations are primarily forwarded to the actual backing store (because that's what matters, and what syncs to the frontend) and there's a longstanding bug where the local instance you have _doesn't_ reflect those updates correctly. It's mostly been a nuisance bug because the typical pattern (referring to component props fully qualified all the time) avoids it.

---

_[View the full topic](https://forum.inductiveautomation.com/t/ign-1660-psa-assigning-values-to-a-property-in-a-script-may-drive-you-nuts/76192)._