# dataQuality inconsistent on components

**URL:** <https://forum.inductiveautomation.com/t/dataquality-inconsistent-on-components/5082>\
**Category:** Ignition\
**Created:** [August 30, 2012, 10:10pm UTC](https://forum.inductiveautomation.com/t/dataquality-inconsistent-on-components/5082 "2012-08-30T22:10:04Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Greg.Buehler](https://avatars.discourse-cdn.com/v4/letter/g/ecc23a/32.png) [@Greg.Buehler](https://forum.inductiveautomation.com/u/Greg.Buehler)\
**Post date:** [August 30, 2012, 10:10pm UTC](https://forum.inductiveautomation.com/t/dataquality-inconsistent-on-components/5082/1 "2012-08-30T22:10:04Z")

</div>

We’re using the ‘dataQuality’ meta-property on one of our windows to determine if the window has completed loading before a script my be ran by the operator. It seems that not all the components have consistent behavior for this property.

For example, the ‘Text Field’ component gives values of -1, 0, and 1 for the quality value with -1 one indicating that the value was still being bound to the component. Whereas the ‘Check Box’ component only gives 0 and 1 for quality values.

---

<div class="post-metadata">

**Author:** ![Michael.Stofan](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michael.stofan/32/3342_2.png) [@Michael.Stofan](https://forum.inductiveautomation.com/u/Michael.Stofan)\
**Post date:** [August 30, 2012, 11:53pm UTC](https://forum.inductiveautomation.com/t/dataquality-inconsistent-on-components/5082/2 "2012-08-30T23:53:11Z")

</div>

The data quality property only shows whether or not a component has had a binding load on any of it’s properties. It really doesn’t have any bearing on when the window itself is finished loading.

At any rate, all components will start with it’s dataquality property at -1. If they have a binding it will change to reflect the state of the binding, and if it doesn’t it will stay at -1.

---

<div class="post-metadata">

**Author:** ![Greg.Buehler](https://avatars.discourse-cdn.com/v4/letter/g/ecc23a/32.png) [@Greg.Buehler](https://forum.inductiveautomation.com/u/Greg.Buehler)\
**Post date:** [August 31, 2012, 1:45pm UTC](https://forum.inductiveautomation.com/t/dataquality-inconsistent-on-components/5082/3 "2012-08-31T13:45:38Z")

</div>

What we’re doing is loading a popup form with data. When the value of the Text Field or Check Box is modified we log the new value and old value to a database with the current user. The problem is that when the form loads and the initial state is set it fires off the propertyChange event so we’re logging x items that are totally irrelevant to our needs. Looking at a components dataQuality as -1 has been pretty reliable on the Text Field components so far, but we need a solution for the Check Boxs.

Any ideas?

---

<div class="post-metadata">

**Author:** ![Travis.Cox](https://avatars.discourse-cdn.com/v4/letter/t/b9bd4f/32.png) [@Travis.Cox](https://forum.inductiveautomation.com/u/Travis.Cox)\
**Post date:** [August 31, 2012, 3:33pm UTC](https://forum.inductiveautomation.com/t/dataquality-inconsistent-on-components/5082/4 "2012-08-31T15:33:32Z")

</div>

What I usually do is add a custom property to the component called firstEvent that is a boolean. Save the window with the value “true” so it always opens that way initially. So when the first propertyChange event happens you check to see if the firstEvent is true and if so do nothing but set the firstEvent to false now. The next time we know it is because they clicked on the component.