# FactoryTalk Transaction Manager AOI replacement?

**URL:** <https://forum.inductiveautomation.com/t/factorytalk-transaction-manager-aoi-replacement/24227>\
**Category:** Ignition\
**Created:** [April 18, 2019, 12:05pm UTC](https://forum.inductiveautomation.com/t/factorytalk-transaction-manager-aoi-replacement/24227 "2019-04-18T12:05:55Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![mcarritt1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mcarritt1/32/4262_2.png) [@mcarritt1](https://forum.inductiveautomation.com/u/mcarritt1)\
**Post date:** [April 18, 2019, 12:05pm UTC](https://forum.inductiveautomation.com/t/factorytalk-transaction-manager-aoi-replacement/24227/1 "2019-04-18T12:05:55Z")

</div>

This might be asking a bit much, but does anyone have an Allen Bradley AOI that they use in place of a FactoryTalk TM AOI? Or just a very reliable Allen Bradley / Ignition Transaction Groups AOI? We recently migrated a customer away from a bunch of FactoryTalk stuff to Ignition, and one of the things I replaced was transaction manager. I wrote my own AOI to do that, which works about 99% of the time… Other times I get duplicate entries and need to go and manually remove them from the database. If anyone has anything in terms of a reliable Allen Bradley AOI for handling hourly database records that would be really helpful.

Unfortunately one of the hurdles is that the recorded time comes from the PLC, and once a year for Daylight savings time, there will be a duplicate entry ( I hate DST SO much…), so unfortunately ticking the box for “only evaluate when values have changed” isn’t an option.

---

<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 18, 2019, 12:14pm UTC](https://forum.inductiveautomation.com/t/factorytalk-transaction-manager-aoi-replacement/24227/2 "2019-04-18T12:14:49Z")

</div>

Consider using the 64-bit wallclock current value (unix epoch microseconds) as your trigger. That’s in UTC and will yield the correct time regardless of DST. Divide by 1000 to pass to system.date.fromMillis().

---

<div class="post-metadata">

**Author:** ![mcarritt1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mcarritt1/32/4262_2.png) [@mcarritt1](https://forum.inductiveautomation.com/u/mcarritt1)\
**Post date:** [April 18, 2019, 12:17pm UTC](https://forum.inductiveautomation.com/t/factorytalk-transaction-manager-aoi-replacement/24227/3 "2019-04-18T12:17:06Z")

</div>

hrm, in this scenario the timestamp really needs to come from the PLC so there’s not really a way around it

---

<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 18, 2019, 12:17pm UTC](https://forum.inductiveautomation.com/t/factorytalk-transaction-manager-aoi-replacement/24227/4 "2019-04-18T12:17:55Z")

</div>

I’m talking about the internal clock of the PLC.