# system.tag.storeTagHistory support in Ignition Edge?

**URL:** <https://forum.inductiveautomation.com/t/system-tag-storetaghistory-support-in-ignition-edge/25169>\
**Category:** Ignition\
**Created:** [May 20, 2019, 7:57pm UTC](https://forum.inductiveautomation.com/t/system-tag-storetaghistory-support-in-ignition-edge/25169 "2019-05-20T19:57:23Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![brian.ankeny](https://avatars.discourse-cdn.com/v4/letter/b/f04885/32.png) [@brian.ankeny](https://forum.inductiveautomation.com/u/brian.ankeny)\
**Post date:** [May 20, 2019, 7:57pm UTC](https://forum.inductiveautomation.com/t/system-tag-storetaghistory-support-in-ignition-edge/25169/1 "2019-05-20T19:57:23Z")

</div>

Does anyone know if system.tag.storeTagHistory (or a similar functionality) is planned to be supported in Edge? For my application, I need the ability to store history for multiple tags relative to a single timestamp and scan classes do not apparently offer that.

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [May 20, 2019, 8:04pm UTC](https://forum.inductiveautomation.com/t/system-tag-storetaghistory-support-in-ignition-edge/25169/2 "2019-05-20T20:04:14Z")

</div>

Probably not - one of the core tenets of Edge is that it _only_ supports going directly through our historian to put data into databases. You’re welcome to submit a feature to [ideas.inductiveautomation.com](http://ideas.inductiveautomation.com) - we have generally allowed more things on Edge over time, but I would say this is fairly unlikely to change.

---

<div class="post-metadata">

**Author:** ![Paul.Scott](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul.scott/32/4578_2.png) [@Paul.Scott](https://forum.inductiveautomation.com/u/Paul.Scott)\
**Post date:** [May 20, 2019, 8:09pm UTC](https://forum.inductiveautomation.com/t/system-tag-storetaghistory-support-in-ignition-edge/25169/3 "2019-05-20T20:09:10Z")

</div>

> [@brian.ankeny](#):
>
> For my application, I need the ability to store history for multiple tags relative to a single timestamp and scan classes do not apparently offer that.

Would you mind elaborating on that? Why exactly wouldn't a scan class help here?

Are you trying to record multiple tag values simultaneously once, instead of polling? If so then a Driven Scan Class with One Shot enabled might give you the functionality you're looking for.

---

<div class="post-metadata">

**Author:** ![brian.ankeny](https://avatars.discourse-cdn.com/v4/letter/b/f04885/32.png) [@brian.ankeny](https://forum.inductiveautomation.com/u/brian.ankeny)\
**Post date:** [May 20, 2019, 8:20pm UTC](https://forum.inductiveautomation.com/t/system-tag-storetaghistory-support-in-ignition-edge/25169/4 "2019-05-20T20:20:45Z")

</div>

Thank you for the suggestion. Unfortunately, I have tried that and ran into issues. See the following post for background:

> [@Ignition Edge: displaying tag history for multiple tags in a table results in multiple rows for identical timestamps](http://forum.inductiveautomation.com/t/ignition-edge-displaying-tag-history-for-multiple-tags-in-a-table-results-in-multiple-rows-for-identical-timestamps/23045):
>
> I am currently working on implementing and Ignition Edge instance which will eventually (hopefully) be used with our existing Ignition server in the future. However, I am experiencing a significant issue displaying tag history queries cleanly. Instead of displaying one row for multiple tags, the query results in multiple rows for identical timestamps (see example below). I also noticed that the entries sometimes show two different values for the same timestamp?? [image] With our Ignition serve…

What I found was that even though I set up the tags to record based on a driven scanclass with a one shot configured, historical tag values in the set had a different timestamps (I had to print the millisecond and microseconds of each timestamp to discover the cause). It would be nice if there was an option to force the scanclass to use a single timestamp.

---

<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:** [May 20, 2019, 9:51pm UTC](https://forum.inductiveautomation.com/t/system-tag-storetaghistory-support-in-ignition-edge/25169/5 "2019-05-20T21:51:45Z")

</div>

You are trying to replicate the functionality of the SQL Bridge module – transaction groups. That isn’t offered in Edge. And all of the ways that would emulate a transaction group require gateway scripting, which also isn’t offered in Edge.

---

<div class="post-metadata">

**Author:** ![kgamble](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kgamble/32/8019_2.png) [@kgamble](https://forum.inductiveautomation.com/u/kgamble)\
**Post date:** [March 17, 2022, 5:28am UTC](https://forum.inductiveautomation.com/t/system-tag-storetaghistory-support-in-ignition-edge/25169/6 "2022-03-17T05:28:46Z")

</div>

Update, this works in 8.1x+ if you have compute and edge sync, just tested!
