# New Feature - Tag Report Tool

**URL:** <https://forum.inductiveautomation.com/t/new-feature-tag-report-tool/61594>\
**Category:** Ignition Early Access\
**Tags:** ignition81\
**Created:** [July 6, 2022, 9:44pm UTC](https://forum.inductiveautomation.com/t/new-feature-tag-report-tool/61594 "2022-07-06T21:44:25Z")\
**Posts on this page:** 1\
**Showing post:** 25

<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:** [August 23, 2022, 4:20pm UTC](https://forum.inductiveautomation.com/t/new-feature-tag-report-tool/61594/25 "2022-08-23T16:20:45Z")

</div>

> [@ggross](#):
>
> While there are things that Phil mentioned that could be done to order the output, there is also a performance cost associated with doing so.

A SQLite index on path and name would probably suffice, and might not be as ugly performance-wise as you think.

Hopefully for v8.2 or so, the source of truth will be JSON on disk instead of in SQLite. If so, please consider using a hierarchy where tag folders are actual folders on disk, UDT definitions and instances are one file each with contents ordered by name, and all other leaf tags in a folder are in a single JSON file, ordered by name.

Make all json diff-friendly with tidyjson/jsonlint/whatever.

Use "version sort" or `AlphaNumComparator` so numbers in tag names are ordered the way humans like.

This above will be very git-friendly and, since each file will be sorted only when edited, should not present a performance problem at other times.

---

_[View the full topic](https://forum.inductiveautomation.com/t/new-feature-tag-report-tool/61594)._