# NULL duplicate values in transaction groups

**URL:** <https://forum.inductiveautomation.com/t/null-duplicate-values-in-transaction-groups/58211>\
**Category:** Ignition\
**Tags:** ignition80\
**Created:** [April 8, 2022, 10:47am UTC](https://forum.inductiveautomation.com/t/null-duplicate-values-in-transaction-groups/58211 "2022-04-08T10:47:04Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![marcos.bartolome](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/marcos.bartolome/32/58225_2.png) [@marcos.bartolome](https://forum.inductiveautomation.com/u/marcos.bartolome)\
**Post date:** [April 8, 2022, 10:47am UTC](https://forum.inductiveautomation.com/t/null-duplicate-values-in-transaction-groups/58211/1 "2022-04-08T10:47:04Z")

</div>

Hi,

We have an ignition edge and an ignition standard connected by gateway network.  
In the standard ignition we have some transaction groups fed from the ignition edge.

A few days ago, we saw that some of this transaction groups datas had been quarantined, the reason it gave was: “This data sink does not accept data of the given type.”. And we saw in the database some duplicate datas with NULL values… Which distorts the results of some queries we have made.

Is there any reason why it could happen?

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/0/2/02cc40c3cc0d2e67e3e3934c9fbe898828442075.jpeg)

---

<div class="post-metadata">

**Author:** ![eduardo.ojalvo](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/eduardo.ojalvo/32/14356_2.png) [@eduardo.ojalvo](https://forum.inductiveautomation.com/u/eduardo.ojalvo)\
**Post date:** [April 8, 2022, 11:38am UTC](https://forum.inductiveautomation.com/t/null-duplicate-values-in-transaction-groups/58211/2 "2022-04-08T11:38:46Z")

</div>

I´d like to add :  
Another thing that you can see and is very weird is that the transaction group is writing 2 register at same time, one with value and other with null.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [April 8, 2022, 11:51am UTC](https://forum.inductiveautomation.com/t/null-duplicate-values-in-transaction-groups/58211/3 "2022-04-08T11:51:08Z")

</div>

Bad quality often yields a null value. How are you accessing the Edge’s data from the standard edition? (Edge doesn’t do transaction groups.)

---

<div class="post-metadata">

**Author:** ![eduardo.ojalvo](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/eduardo.ojalvo/32/14356_2.png) [@eduardo.ojalvo](https://forum.inductiveautomation.com/u/eduardo.ojalvo)\
**Post date:** [April 8, 2022, 1:10pm UTC](https://forum.inductiveautomation.com/t/null-duplicate-values-in-transaction-groups/58211/4 "2022-04-08T13:10:33Z")

</div>

With a gateway network, we have an a hub&sopke architecture.

---

<div class="post-metadata">

**Author:** ![eduardo.ojalvo](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/eduardo.ojalvo/32/14356_2.png) [@eduardo.ojalvo](https://forum.inductiveautomation.com/u/eduardo.ojalvo)\
**Post date:** [April 8, 2022, 1:11pm UTC](https://forum.inductiveautomation.com/t/null-duplicate-values-in-transaction-groups/58211/5 "2022-04-08T13:11:06Z")

</div>

historical provider from gateway network

---

<div class="post-metadata">

**Author:** ![marcos.bartolome](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/marcos.bartolome/32/58225_2.png) [@marcos.bartolome](https://forum.inductiveautomation.com/u/marcos.bartolome)\
**Post date:** [April 19, 2022, 6:58am UTC](https://forum.inductiveautomation.com/t/null-duplicate-values-in-transaction-groups/58211/6 "2022-04-19T06:58:26Z")

</div>

As my partner Eduardo says, we have a gateway network incoming conexion, from where we read the tag from the edge.  
So, in the transaction group (in the ignition broker, an ignition Standard), the tag path looks like “[STATION\_edge]Edge Nodes/hidros/station/…”, which means that we are reading the tag from the gateway network conexion… I don’t know if there is another way to do it without duplicating the tags in the Ignition Standard with reference o derived tag.

Regards.