# \[DONE\] "Hint" field for entities **URL:** \ **Category:** Ideas & Features\ **Created:** [June 6, 2022, 11:52pm UTC](https://community.fibery.io/t/done-hint-field-for-entities/2917 "2022-06-06T23:52:38Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Matt\_Blais](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/matt_blais/32/1464_2.png) [@Matt\_Blais](https://community.fibery.io/u/Matt_Blais)\ **Post date:** [June 6, 2022, 11:52pm UTC](https://community.fibery.io/t/done-hint-field-for-entities/2917/1 "2022-06-06T23:52:38Z")
I suggest the capability to designate a Text/Formula field in a DB as the “Hint” field for the DB. The hint field’s contents would be displayed in a hint balloon whenever the entity name or link is hovered-over, in any view (e.g. in a relation cell in a Table). **Use case:** I create “Icon” Formula fields everywhere, as a way to represent an entity’s type or status graphically. It would be awesome if hovering over one of these fields for example could show a popup hint describing the icon’s meaning: ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/0/00c67c5a0300f9163c758c4fc7793ec401652ba8.png) In the case where no hint is defined for an entity, the entity’s full Name field could be displayed as the hint (there are many situations, such as relations in a Table View, where the entity’s full name may be too long to be displayed in full). ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [June 7, 2022, 5:42am UTC](https://community.fibery.io/t/done-hint-field-for-entities/2917/2 "2022-06-07T05:42:37Z")
Are you suggesting that the hint would ideally be definable per entity? ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [June 7, 2022, 6:32am UTC](https://community.fibery.io/t/done-hint-field-for-entities/2917/3 "2022-06-07T06:32:11Z")
Why? I think per-Database field. If you know outcome you can describe it in this hint. ---
**Author:** ![Matt\_Blais](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/matt_blais/32/1464_2.png) [@Matt\_Blais](https://community.fibery.io/u/Matt_Blais)\ **Post date:** [June 7, 2022, 2:16pm UTC](https://community.fibery.io/t/done-hint-field-for-entities/2917/4 "2022-06-07T14:16:49Z")
> [@Chr1sG](#): > > Are you suggesting that the hint would ideally be definable per entity? Ideally the hint content could be customized for what exactly is hovered-over. To be truly flexible that would require the possibility to define a separate hint (Formula) for every field in a DB. Or else a Formula that can tell which field is being hovered over, and its value. ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [June 7, 2022, 2:30pm UTC](https://community.fibery.io/t/done-hint-field-for-entities/2917/5 "2022-06-07T14:30:47Z")
I agree that there would ideally be a hint for every field, as well as a hint for the database. But if you’re suggesting using text fields as holders for hints, this implies that you need 2n+1 fields to support n functional fields 🤔 And I don’t think it is likely that users want the hint to vary by entity within the same database. Maybe I misunderstood what you meant by > [@Matt\_Blais](#): > > designate a Text/Formula field in a DB as the “Hint” field ---
**Author:** ![Matt\_Blais](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/matt_blais/32/1464_2.png) [@Matt\_Blais](https://community.fibery.io/u/Matt_Blais)\ **Post date:** [June 7, 2022, 2:52pm UTC](https://community.fibery.io/t/done-hint-field-for-entities/2917/6 "2022-06-07T14:52:10Z")
You didn’t misunderstand – I just hadn’t thought through all the ways this might work. I agree that defining a new, separate field for (potentially) every existing field in a DB is unwieldy. The first level is just the ability to have a static description for every field (e.g. “Date person registered - Leave blank if unknown”, or a table with explanations of each Single Select value). It would also be interesting to also be able to customize a field’s Hint according to its current content, which would mean a Formula instead of static text for the field’s Hint. 🤔 ---
**Author:** ![Polina\_Zenevich](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/polina_zenevich/32/480_2.png) [@Polina\_Zenevich](https://community.fibery.io/u/Polina_Zenevich)\ **Post date:** [October 25, 2022, 1:45pm UTC](https://community.fibery.io/t/done-hint-field-for-entities/2917/7 "2022-10-25T13:45:16Z")
Some good news - that’s done 🙂 > [@CHANGELOG: October 20, 2022 / Customize mentions, Field description](https://community.fibery.io/t/changelog-october-20-2022-customize-mentions-field-description/3434): > > nail_care Customize Fields for Entity mentions [customize-units-mentions] Wouldn’t it be nice to see something apart from the name of a mentioned thing? Maybe not even State or Assignees but something different? Customize Fields for each Database to provide readers with more click-free context: Due Date for Tasks Customer and Customer Status for Feedback Notes Amount and Probability for Deals (you name it) thinking Field description It’s not always obvious from a Field na… ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [November 22, 2022, 3:24pm UTC](https://community.fibery.io/t/done-hint-field-for-entities/2917/8 "2022-11-22T15:24:32Z")