# Transactional group evaluate on change

**URL:** <https://forum.inductiveautomation.com/t/transactional-group-evaluate-on-change/1502>\
**Category:** Ignition\
**Created:** [February 6, 2010, 6:45pm UTC](https://forum.inductiveautomation.com/t/transactional-group-evaluate-on-change/1502 "2010-02-06T18:45:32Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![david\_mccutchen](https://avatars.discourse-cdn.com/v4/letter/d/919ad9/32.png) [@david\_mccutchen](https://forum.inductiveautomation.com/u/david_mccutchen)\
**Post date:** [February 6, 2010, 6:45pm UTC](https://forum.inductiveautomation.com/t/transactional-group-evaluate-on-change/1502/1 "2010-02-06T18:45:32Z")

</div>

The group setting “evaluate on change” does not seem to work. I have 1 item in a group that I know is not changing, but the group triggers and writes on the update rate regardless. I am wondering if it is also looking at the t\_stamp or quality code. I used the custom setting and still got the same results.  
Also a minor thing, by default the “delete by” box selects ms. I think this is from the legacy import. If I add a new group it doesn’t do this. When you drop it down it has day,month,year and they select fine.

---

<div class="post-metadata">

**Author:** ![david\_mccutchen](https://avatars.discourse-cdn.com/v4/letter/d/919ad9/32.png) [@david\_mccutchen](https://forum.inductiveautomation.com/u/david_mccutchen)\
**Post date:** [February 10, 2010, 3:04pm UTC](https://forum.inductiveautomation.com/t/transactional-group-evaluate-on-change/1502/2 "2010-02-10T15:04:45Z")

</div>

Bump

---

<div class="post-metadata">

**Author:** ![Colby.Clegg](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/colby.clegg/32/3282_2.png) [@Colby.Clegg](https://forum.inductiveautomation.com/u/Colby.Clegg)\
**Post date:** [February 10, 2010, 5:37pm UTC](https://forum.inductiveautomation.com/t/transactional-group-evaluate-on-change/1502/3 "2010-02-10T17:37:03Z")

</div>

Ah! Sorry, I thought I had replied to this. Indeed, there was a problem, and it’s been fixed for 7.0.2 which will be released very shortly.

Regards,
