# Adding some context of referring Entity to Highlights References

**URL:** <https://community.fibery.io/t/adding-some-context-of-referring-entity-to-highlights-references/895>\
**Category:** Ideas & Features\
**Created:** [August 12, 2020, 3:40am UTC](https://community.fibery.io/t/adding-some-context-of-referring-entity-to-highlights-references/895 "2020-08-12T03:40:34Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![B\_Sp](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@B\_Sp](https://community.fibery.io/u/B_Sp)\
**Post date:** [August 12, 2020, 3:40am UTC](https://community.fibery.io/t/adding-some-context-of-referring-entity-to-highlights-references/895/1 "2020-08-12T03:40:34Z")

</div>

Hi guys,

As I use references more and more - and thanks again for the great feature - I am noticing that it would be helpful if the context of the mentioning Entity also came across in the reference. This is relevant particularly in these cases:

- Distinguishing if a reference was in an Entity’s main “body,” or comment stream, as both can have entities

- If you are using Rich Text fields for multiple purposes. Incidentally this is a huge bonus of Fibery that you can create many Rich Text fields. For example, in the case of “Projects” you could have things like “Project Goal,” “Requirements,” “Questions” and “Project Conclusion.”

In the case of references in each of those Rich Text areas, it would be great if you could see where the reference happened. Otherwise you just see that the reference was in the “Project” entity, but a good deal of context is lost because you don’t know the rest of the context of where that reference was written. **There is a big difference if it was written in the “Project Goal” vs “Project Conclusion” sections**

Thanks guys!

 ![Image 2020-08-12 at 12.38.52 AM.png](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/f/ff42f06b450ea8579f987564313fb76603692d85.png)

---

<div class="post-metadata">

**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\
**Post date:** [August 21, 2020, 10:27pm UTC](https://community.fibery.io/t/adding-some-context-of-referring-entity-to-highlights-references/895/2 "2020-08-21T22:27:56Z")

</div>

I like this idea. Maybe just the option to display the Field where the reference occurred?

---

<div class="post-metadata">

**Author:** ![B\_Sp](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@B\_Sp](https://community.fibery.io/u/B_Sp)\
**Post date:** [August 22, 2020, 1:21am UTC](https://community.fibery.io/t/adding-some-context-of-referring-entity-to-highlights-references/895/3 "2020-08-22T01:21:07Z")

</div>

Hey @Oshyan thanks for the support on this one!

I am wondering if in the next release of Back References referred to as “Bi-Directional linked text,” referenced below, we might see this?

> <https://twitter.com/fibery_io/status/1295704352900907008?s=20>

Would be great to hear from @mdubakov or one of the team, perhaps @Polina_Zenevich, on this!

Thanks!

---

<div class="post-metadata">

**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:** [August 24, 2020, 11:26am UTC](https://community.fibery.io/t/adding-some-context-of-referring-entity-to-highlights-references/895/4 "2020-08-24T11:26:05Z")

</div>

Hi, guys 🙂  
Many thanks for the idea!  
Telling the truth, that feature wasn’t in our highlights scope. So, Highlights will appear soon, but it would be released without this opportunity.

Anyway your case makes sense, so we would discuss that a bit later and see, what we can do 🧐

Thanks again! 🤗✨

---

<div class="post-metadata">

**Author:** ![B\_Sp](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@B\_Sp](https://community.fibery.io/u/B_Sp)\
**Post date:** [August 25, 2020, 4:56am UTC](https://community.fibery.io/t/adding-some-context-of-referring-entity-to-highlights-references/895/5 "2020-08-25T04:56:01Z")

</div>

Thank you Polina, that is great to hear that you guys would consider this!

---

<div class="post-metadata">

**Author:** ![B\_Sp](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@B\_Sp](https://community.fibery.io/u/B_Sp)\
**Post date:** [October 23, 2020, 1:43am UTC](https://community.fibery.io/t/adding-some-context-of-referring-entity-to-highlights-references/895/6 "2020-10-23T01:43:38Z")

</div>

As a follow up on this request, I wanted to add that in addition to the Rich Text and Comments where a highlight can occur, I think the “small” text field is another area where, should this request be realized:

> [@More "Rich Text" in simple Text Box](https://community.fibery.io/t/more-rich-text-in-simple-text-box/984):
>
> I am trying to set up one of the features of both Coda and Notion that I found very useful and would love to be able to do in Fibery - use a “join” entity to show deep info between other entities. Ideally I’d like to be able to type into this Entity within another, for example during meetings. While we are waiting on the visibility of Rich Text fields within Tables and Collections, from this post: I think it would be very helpful to have some more ability in the “Text Box” Field: Ability …

it would also make sense to show in Highlights if this type of field is where a reference takes place.

In my use of both Notion and Coda, you can create unlimited “small” text fields that show up in embedded views, like Table or “Collections” in Fibery, and you can customize what you want these fields to represent, like a “Project Outcome” or other useful context. So it would be great to see them also represented in Highlights.

Thanks for the consideration!

---

<div class="post-metadata">

**Author:** ![B\_Sp](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@B\_Sp](https://community.fibery.io/u/B_Sp)\
**Post date:** [December 30, 2020, 1:01am UTC](https://community.fibery.io/t/adding-some-context-of-referring-entity-to-highlights-references/895/7 "2020-12-30T01:01:35Z")

</div>

Hi guys, just wanted to bump this up again. I know you’ve responded with some positive from @Polina_Zenevich that you will consider it. Just wanted to add that my team is really getting into Highlights and we use a lot of Rich Text fields (like in my example at the top) across different entities, and utilize Comments a great deal, so it would be very useful to be able to see where the reference is within the Referring Entity.

Perhaps this could go on your list for Lookups 2.0?

> [@Lookups from Comments, just like References - useful for Project Mgmt/CRM](https://community.fibery.io/t/lookups-from-comments-just-like-references-useful-for-project-mgmt-crm/1250/3):
>
> We have a feature LookUp field 2.0 - and there we collect all the ideas about this field improvement.  
> Linked your suggestion 🧐🔥

Thank you as always!

---

<div class="post-metadata">

**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:** [December 30, 2020, 2:31pm UTC](https://community.fibery.io/t/adding-some-context-of-referring-entity-to-highlights-references/895/8 "2020-12-30T14:31:57Z")

</div>

Hi!  
Telling the truth, we didn’t touch on that issue at all since you mentioned it.  
Currently, we focus on finishing all the product features, fixing bugs, and moving infrastructure.  
I will let you know once there will be any update about this (not sure that would be soon, telling the truth, but who knows 🧐)

---

<div class="post-metadata">

**Author:** ![B\_Sp](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@B\_Sp](https://community.fibery.io/u/B_Sp)\
**Post date:** [January 1, 2021, 4:26pm UTC](https://community.fibery.io/t/adding-some-context-of-referring-entity-to-highlights-references/895/9 "2021-01-01T16:26:15Z")

</div>

Ok thanks Polina I appreciate the update!
