# Force Tag Historian to use tag path case

**URL:** <https://forum.inductiveautomation.com/t/force-tag-historian-to-use-tag-path-case/34516>\
**Category:** Ignition\
**Created:** [May 7, 2020, 7:54am UTC](https://forum.inductiveautomation.com/t/force-tag-historian-to-use-tag-path-case/34516 "2020-05-07T07:54:00Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\
**Post date:** [May 7, 2020, 7:54am UTC](https://forum.inductiveautomation.com/t/force-tag-historian-to-use-tag-path-case/34516/1 "2020-05-07T07:54:00Z")

</div>

By default, the tag historian adds tags into the SQL table and forces lower-case on the tag path. When displaying this tag path to the user, whether it’s via a tag treeview component or otherwise, this looks unprofessional and often makes the tag paths difficult to read (especially if you’ve used CamelCase).

Is it possible to force Tag Historian not to lower the case? I’m thinking about updating the entries within the `sqth_te` table… but it’s not going to be fun!

---

<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 7, 2020, 11:59am UTC](https://forum.inductiveautomation.com/t/force-tag-historian-to-use-tag-path-case/34516/2 "2020-05-07T11:59:29Z")

</div>

Expect breakage if you edit sqlth\_te. I’d expect the historian to be using efficient case-sensitive indices, which requires normalizing the case. But those are small tables, so it might not be too bad. Consider putting this on the ideas site.

---

<div class="post-metadata">

**Author:** ![MMaynard](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mmaynard/32/3366_2.png) [@MMaynard](https://forum.inductiveautomation.com/u/MMaynard)\
**Post date:** [May 7, 2020, 12:33pm UTC](https://forum.inductiveautomation.com/t/force-tag-historian-to-use-tag-path-case/34516/3 "2020-05-07T12:33:43Z")

</div>

We add fields to the sqlth\_te table for tagname and group name.  
We then fill these in with scripting from the Tooltip field of the history tag.  
Then we use a scripted Treeview to display the tags for the end users.  
This way we control the displayed name for the tags in a manner the operators understand.

---

<div class="post-metadata">

**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\
**Post date:** [May 7, 2020, 10:19pm UTC](https://forum.inductiveautomation.com/t/force-tag-historian-to-use-tag-path-case/34516/4 "2020-05-07T22:19:52Z")

</div>

Sounds like a good idea! I haven’t tried scripting a tree view. Do you offer filtering of tags to the operator? If so, how fast is the refresh rate of your tree view?  
I’ve been using a simple List box which just queries the tag table, so filtering is super fast as it’s just am sql query filter. Without a filter for the sites I work at (wineries with many tanks), it would be a frustrating experience for the operators to add tags

---

<div class="post-metadata">

**Author:** ![MMaynard](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mmaynard/32/3366_2.png) [@MMaynard](https://forum.inductiveautomation.com/u/MMaynard)\
**Post date:** [May 8, 2020, 12:09pm UTC](https://forum.inductiveautomation.com/t/force-tag-historian-to-use-tag-path-case/34516/5 "2020-05-08T12:09:28Z")

</div>

Same way as you are doing it, the treeview datasource is a query. 🙂