# Heaps of Tags and Reporting Changes

**URL:** <https://forum.inductiveautomation.com/t/heaps-of-tags-and-reporting-changes/15373>\
**Category:** Ignition\
**Created:** [September 16, 2017, 3:03pm UTC](https://forum.inductiveautomation.com/t/heaps-of-tags-and-reporting-changes/15373 "2017-09-16T15:03:07Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![CHenley](https://avatars.discourse-cdn.com/v4/letter/c/7ab992/32.png) [@CHenley](https://forum.inductiveautomation.com/u/CHenley)\
**Post date:** [September 16, 2017, 3:03pm UTC](https://forum.inductiveautomation.com/t/heaps-of-tags-and-reporting-changes/15373/1 "2017-09-16T15:03:08Z")

</div>

Ignition Gateway 7.8.4  
Currently at 42,181 tags / 18 scan classes

**A little background**  
Have been developing a wash system timers program for supervision to make changes to step times within the wash systems. Currently using a template (as shown below), this is bound to tags using the custom properties. On the main window of the client, basically making the templates visibility change depending on which radio button is selected and what is selected on the dropdown list. The scanclass is set to a 0 poll rate and is working on updating the tag within the PLC on a change from the designer.

 ![](https://us1.discourse-cdn.com/inductiveautomation/original/2X/7/74d8bb973c78fc10ad6756e258cc26603592c536.jpg)  
 ![](https://us1.discourse-cdn.com/inductiveautomation/original/2X/a/aa89153d820290bb676dc4561b5b74d4afe4ce42.jpg)  
 ![](https://us1.discourse-cdn.com/inductiveautomation/original/2X/8/852529506435da19b37735e289b23b1ff973fbef.jpg)

**My Question Is:**  
We would like to log changes made to the timers which the following information:  
Date, Time, Client Host, User, Tag Changed, Tag’s Previous Value, Tag’s New Value

What would be the proper way to go about this? Have looked at transaction manager, tag event scripting, historical (tag history value on change). Getting lost within researching a valid method on how to report this. We wouldn’t need to worry about tracking the tag values being changed on the PLC itself. So what’s the best route???

Thanks in advance,

Cameron

---

<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:** [September 18, 2017, 4:00pm UTC](https://forum.inductiveautomation.com/t/heaps-of-tags-and-reporting-changes/15373/2 "2017-09-18T16:00:49Z")

</div>

[Project Auditing](https://docs.inductiveautomation.com/display/DOC/Project+Auditing) seems like it might cover almost all of your requirements with a minimum amount of extra effort required.

---

<div class="post-metadata">

**Author:** ![CHenley](https://avatars.discourse-cdn.com/v4/letter/c/7ab992/32.png) [@CHenley](https://forum.inductiveautomation.com/u/CHenley)\
**Post date:** [September 23, 2017, 1:26pm UTC](https://forum.inductiveautomation.com/t/heaps-of-tags-and-reporting-changes/15373/3 "2017-09-23T13:26:17Z")

</div>

Thanks, that ended up working by parsing out the ACTION\_TARGET through SQL.