# propertyChange problem in Parameterized Windows

**URL:** <https://forum.inductiveautomation.com/t/propertychange-problem-in-parameterized-windows/9477>\
**Category:** Ignition\
**Created:** [December 22, 2014, 5:47pm UTC](https://forum.inductiveautomation.com/t/propertychange-problem-in-parameterized-windows/9477 "2014-12-22T17:47:16Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![bryce.troy](https://avatars.discourse-cdn.com/v4/letter/b/ecb155/32.png) [@bryce.troy](https://forum.inductiveautomation.com/u/bryce.troy)\
**Post date:** [December 22, 2014, 5:47pm UTC](https://forum.inductiveautomation.com/t/propertychange-problem-in-parameterized-windows/9477/1 "2014-12-22T17:47:16Z")

</div>

I am trying to log setpoint value changes using a Transaction Group triggered by propertyChange events on the text field components of several parameterized windows. Problem is that whenever the window is reopened with new parameters, some of the components (the ones which have different values from the previous instance) fire a propertyChange event. What is the best way to ignore these initial events? I am thinking about adding a timer to the window and ignoring any events in the first second or two that the window is opened. Is there a more elegant solution?

Thanks - Bryce  
Left Hand Brewing Company

---

<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:** [December 23, 2014, 5:44pm UTC](https://forum.inductiveautomation.com/t/propertychange-problem-in-parameterized-windows/9477/2 "2014-12-23T17:44:48Z")

</div>

Hi Bryce,

Been mulling this for a bit-- usually in between Christmas cookies… ![:thumb_right:](https://us1.discourse-cdn.com/inductiveautomation/original/1X/2026e28c0c425034352c1b75807edf956adc75f4.gif ":thumb\_right:")

I was wondering if this would be better handled by the built-in auditing within Ignition.

---

<div class="post-metadata">

**Author:** ![bryce.troy](https://avatars.discourse-cdn.com/v4/letter/b/ecb155/32.png) [@bryce.troy](https://forum.inductiveautomation.com/u/bryce.troy)\
**Post date:** [December 24, 2014, 9:06pm UTC](https://forum.inductiveautomation.com/t/propertychange-problem-in-parameterized-windows/9477/3 "2014-12-24T21:06:11Z")

</div>

Jordan - Good thought, but setpoint changes can come from either authorized Ignition users or from A-B HMIs on the production floor. I want to know from whence the setpoint came, and by whom. Therefore, I have setpoint input fields on both Ignition and HMI screens trigger the Transaction Group to log the change with appropriate information. I haven’t really used auditing - could it account for changes made from outside Ignition?

Time for some Christmas Eve beer and cookies . . .