# Tag Historian Help Please **URL:** \ **Category:** Ignition\ **Created:** [August 26, 2021, 5:32pm UTC](https://forum.inductiveautomation.com/t/tag-historian-help-please/50345 "2021-08-26T17:32:15Z")\ **Posts on this page:** 1\ **Showing post:** 8
**Author:** ![leonardo.godoi](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/leonardo.godoi/32/27178_2.png) [@leonardo.godoi](https://forum.inductiveautomation.com/u/leonardo.godoi)\ **Post date:** [August 26, 2021, 7:07pm UTC](https://forum.inductiveautomation.com/t/tag-historian-help-please/50345/8 "2021-08-26T19:07:42Z")
> [@jbpingston](#): > > Would I have to do a new transaction group for each PartData position?? i.e. - PartData1, PartData2, etc If you'll only access this data inside ignition, stick with historian, it'll do a great job storing your data, be it bools, ints, floats, strings, etc... > [@jbpingston](#): > > The customer basically wants timestamps to track a part This seems like a good case to bring all this data into a comprehensive report where you can search the serial number or something, you could also just show this data using the power table and the easy chart with maybe a separate subplot for the digital tags. This kind of thing is kinda hard to say what to do without knowing very well how things work in the plant, but if you're looking for inspiration definetly take a look here, especially the more recent projects from 2018 onwards: > [@Project screenshots - share yours](https://forum.inductiveautomation.com/t/project-screenshots-share-yours/513/32): > > Just saw this thread…here are some, probably 50 or so more… You don't need to do the same complex things people have done but this and the section on the documentation about High performance HMI and books helped me a lot in having a better idea on how to show data in a way that makes sense --- _[View the full topic](https://forum.inductiveautomation.com/t/tag-historian-help-please/50345)._