# propertyChange in a template

**URL:** <https://forum.inductiveautomation.com/t/propertychange-in-a-template/42708>\
**Category:** Ignition\
**Created:** [January 28, 2021, 4:48pm UTC](https://forum.inductiveautomation.com/t/propertychange-in-a-template/42708 "2021-01-28T16:48:45Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![JordanCClark](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jordancclark/32/83362_2.png) [@JordanCClark](https://forum.inductiveautomation.com/u/JordanCClark)\
**Post date:** [January 29, 2021, 10:45am UTC](https://forum.inductiveautomation.com/t/propertychange-in-a-template/42708/7 "2021-01-29T10:45:54Z")

</div>

This may help

> [@Ignore propertyChange script on load](http://forum.inductiveautomation.com/t/ignore-propertychange-script-on-load/18190/2):
>
> I usually solve these sorts of problems by modifying the bindings supplying the initial values to the entry fields. Specifically, I add custom properties for the “raw” or incoming value, and uni-directionally bind the component’s value field (dateValue in this case) to that custom property. Then in your existing propertyChange scripts, also check if the new value matches the custom property. If so, it wasn’t operator entry, and that event can be ignored.

---

_[View the full topic](https://forum.inductiveautomation.com/t/propertychange-in-a-template/42708)._