# Block Transaction Group - Clearing Latched Values

**URL:** <https://forum.inductiveautomation.com/t/block-transaction-group-clearing-latched-values/38580>\
**Category:** Ignition\
**Created:** [September 10, 2020, 10:18pm UTC](https://forum.inductiveautomation.com/t/block-transaction-group-clearing-latched-values/38580 "2020-09-10T22:18:28Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![andrew.harrison](https://avatars.discourse-cdn.com/v4/letter/a/85f322/32.png) [@andrew.harrison](https://forum.inductiveautomation.com/u/andrew.harrison)\
**Post date:** [September 10, 2020, 10:18pm UTC](https://forum.inductiveautomation.com/t/block-transaction-group-clearing-latched-values/38580/1 "2020-09-10T22:18:28Z")

</div>

I am experimenting with Block Groups and am trying to use Ignition to filter records from a table by passing WHERE conditions from the PLC. The selected values are then mapped back to the PLC.  
It seems to basically work except once a value is set in the Latched Value field, I cannot clear. it.

For instance, if I trigger the group and the WHERE clause returns 6 values, the Latched and Source Values are correct. But if I then change the conditions so that only 1 value is returned and retrigger, the result is placed in position 0 but the other 5 values are retained from the previous query.

I can clear the Source Values by writing them in the PLC before triggering the group but the latched values just come back.

I found the section in the help about “Setting NULL DB Values to Default”, but whichever options I check, the group behaves the same.

Any help will be greatly appreciated!

---

<div class="post-metadata">

**Author:** ![Paullys50](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paullys50/32/3324_2.png) [@Paullys50](https://forum.inductiveautomation.com/u/Paullys50)\
**Post date:** [September 10, 2020, 10:45pm UTC](https://forum.inductiveautomation.com/t/block-transaction-group-clearing-latched-values/38580/2 "2020-09-10T22:45:01Z")

</div>

It’s a bug that I reported back in version 8.0.5, definitely an issue if the values are getting written to a PLC for any real control purposes.
