# Can't fully customize displayed order of fields in many views

**URL:** <https://community.fibery.io/t/cant-fully-customize-displayed-order-of-fields-in-many-views/3522>\
**Category:** Bugs & Issues\
**Created:** [November 11, 2022, 8:00pm UTC](https://community.fibery.io/t/cant-fully-customize-displayed-order-of-fields-in-many-views/3522 "2022-11-11T20:00:09Z")\
**Posts on this page:** 5\
**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:** [November 11, 2022, 8:00pm UTC](https://community.fibery.io/t/cant-fully-customize-displayed-order-of-fields-in-many-views/3522/1 "2022-11-11T20:00:09Z")

</div>

Bug or feature? It seems that the `Name` and `DB Icon` fields must always always be first, and there are other situations where re-ordering of fields is limited or impossible (see below):

* * *

**Card View:**

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/2/290c09f8a27db5d11cfa7b44a8ded75d688a9499.png)

* * *

**In Entity View (showing a collection via a Lookup field):**

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/e/e9423f3610a45d34f337129bface2700eee5f317.png)

* * *

**In Entity View (showing a List view of a M2M relation):**

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/f/f1773dee6e9d7e653844fa7f9ed785c85ebb00b9.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:** [November 11, 2022, 8:28pm UTC](https://community.fibery.io/t/cant-fully-customize-displayed-order-of-fields-in-many-views/3522/2 "2022-11-11T20:28:35Z")

</div>

I won’t comment on whether it is desirable behaviour or not, but it is the designed behaviour that certain fields are not relocatable (name, db icon/badge, avatars etc.)

And yes, there are some representations of collection fields (e.g. lookups) where the field order is not adjustable at all. This is suboptimal, but has yet to receive the developer attention needed.

---

<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:** [November 11, 2022, 9:29pm UTC](https://community.fibery.io/t/cant-fully-customize-displayed-order-of-fields-in-many-views/3522/3 "2022-11-11T21:29:05Z")

</div>

I have at least one case where the Names of my entities (via formula) are actually the names of their Workflow state (e.g. “Progress”, “Done”, etc). Which is what I want… but, in certain views I would rather have these entities displayed with a different field first, such as the Name of a related entity.

---

<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:** [November 12, 2022, 8:49am UTC](https://community.fibery.io/t/cant-fully-customize-displayed-order-of-fields-in-many-views/3522/4 "2022-11-12T08:49:13Z")

</div>

In that case, you could just hide the Name field and show the related entity field and the State field.  
Then you can choose their respective order.

---

<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:** [November 15, 2022, 12:14pm UTC](https://community.fibery.io/t/cant-fully-customize-displayed-order-of-fields-in-many-views/3522/5 "2022-11-15T12:14:26Z")

</div>

Some updates here!  
That’s not a bug, because that’s the way it was designed and there is no easy way to fix that 😅  
But we have this in plans for someday and your case has to be covered 🙂

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/1/17c0417e9ebcd8130cb9bd3c96c7e022fe3a2f9f.png)
