# Inconsistent formatting of Collection fields in entity views

**URL:** <https://community.fibery.io/t/inconsistent-formatting-of-collection-fields-in-entity-views/4040>\
**Category:** Bugs & Issues\
**Tags:** entity-view\
**Created:** [February 23, 2023, 3:08am UTC](https://community.fibery.io/t/inconsistent-formatting-of-collection-fields-in-entity-views/4040 "2023-02-23T03:08:27Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**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:** [February 23, 2023, 3:08am UTC](https://community.fibery.io/t/inconsistent-formatting-of-collection-fields-in-entity-views/4040/1 "2023-02-23T03:08:27Z")

</div>

Not sure how much of this is intentional, but the inconsistency looks unprofessional.

- Different font size and weight between field name of collection lookups vs. native collections
- Different background colors, even between two collection lookups
- Collection lookups are missing the DB Icon that is displayed for native collections
- Cannot create additional views for collection lookups, as we can on native collections
- The “expansion caret” `>` is always visible for collapsed collections, but only visible _on hover_ for expanded collections.
- The “expansion caret” for collection lookups is slightly offset from the caret for native collections

 ![image|1114×1036](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/f/f7ee55d97047fd5159c2734703e8f9d917efe025.png)

---

<div class="post-metadata">

**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:** [February 23, 2023, 4:44pm UTC](https://community.fibery.io/t/inconsistent-formatting-of-collection-fields-in-entity-views/4040/2 "2023-02-23T16:44:52Z")

</div>

When the ‘new’ relation views were rolled out, it wasn’t easy to implement them for read-only fields (like lookups and formula fields). As a result, these field continued to utilise the ‘old’ relation field UI.
