# \[IGN-6501\]Tag database NOT showing custom tooltips on UDT tags

**URL:** <https://forum.inductiveautomation.com/t/ign-6501-tag-database-not-showing-custom-tooltips-on-udt-tags/63238>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [August 20, 2022, 4:27pm UTC](https://forum.inductiveautomation.com/t/ign-6501-tag-database-not-showing-custom-tooltips-on-udt-tags/63238 "2022-08-20T16:27:39Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Chris\_Bingham](https://avatars.discourse-cdn.com/v4/letter/c/e5b9ba/32.png) [@Chris\_Bingham](https://forum.inductiveautomation.com/u/Chris_Bingham)\
**Post date:** [August 20, 2022, 4:27pm UTC](https://forum.inductiveautomation.com/t/ign-6501-tag-database-not-showing-custom-tooltips-on-udt-tags/63238/1 "2022-08-20T16:27:39Z")

</div>

Ignition 8.1.18:  
If I configure a tooltip on a Standard Tag (currently, “This is a tooltip!”), I am able to see the tooltip when hovering over a tag within the tag database:  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/f/2/f2979beb6203babc2188efd53373419aa2c9f890.png)

However, if I configure a tooltip on a Data Type Instance (from UDT definition: “This is a UDT tooltip!”), I am unable to see the tooltip during hover:  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/8/e/8e3389dc35e2b97d6623f48404917880d309eb81.png)

End goal is to display the tag description, as-defined from a parameter configured in the UDT. Unsure if this is a bug, or if I need to configure a setting somewhere in order to see tooltips on UDTs. Any suggestions?

---

<div class="post-metadata">

**Author:** ![Ken\_Pace](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ken_pace/32/36092_2.png) [@Ken\_Pace](https://forum.inductiveautomation.com/u/Ken_Pace)\
**Post date:** [August 22, 2022, 4:00pm UTC](https://forum.inductiveautomation.com/t/ign-6501-tag-database-not-showing-custom-tooltips-on-udt-tags/63238/2 "2022-08-22T16:00:02Z")

</div>

Thanks for the report - this appears to be a bug and I’ve filed a ticket to track it.
