# Unable to sort decending

**URL:** <https://community.fibery.io/t/unable-to-sort-decending/7792>\
**Category:** Bugs & Issues\
**Created:** [November 14, 2024, 7:31am UTC](https://community.fibery.io/t/unable-to-sort-decending/7792 "2024-11-14T07:31:50Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![sternkern](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/sternkern/32/10500_2.png) [@sternkern](https://community.fibery.io/u/sternkern)\
**Post date:** [November 14, 2024, 7:31am UTC](https://community.fibery.io/t/unable-to-sort-decending/7792/1 "2024-11-14T07:31:50Z")

</div>

Hi All!

I have been having an issue with sorting any data by date in a descending order.  
Even if I use a single sorting expression in a formula I always get an ascending list.  
Eg.:

Runs.Filter([Creation Date] \>= Today() - Days(15)).Sort(Finished, false)

will result the same list as

Runs.Filter([Creation Date] \>= Today() - Days(15)).Sort(Finished)

Has anybody else noticed a similar behavior?  
Thank You!  
Attila

---

<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 14, 2024, 7:35am UTC](https://community.fibery.io/t/unable-to-sort-decending/7792/2 "2024-11-14T07:35:49Z")

</div>

The `Sort()` function is normally only used in formulas when followed by `First()` or `Last()`, in order to [get the highest/lowest item](https://the.fibery.io/@public/User_Guide/Guide/Formulas-Reference-44/anchor=Sort(-field,-isAscending-)-+-First()-and--e854f229-3f1e-4ca7-9f49-1901823c5286). It has no effect on how a collection is displayed on the UI.  
Sorting of a collection is a UI-only thing, and for formulas that result in a collection, it is not possible to control the sort order.

---

<div class="post-metadata">

**Author:** ![sternkern](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/sternkern/32/10500_2.png) [@sternkern](https://community.fibery.io/u/sternkern)\
**Post date:** [November 14, 2024, 8:10am UTC](https://community.fibery.io/t/unable-to-sort-decending/7792/3 "2024-11-14T08:10:02Z")

</div>

Thank You, Chr1sG for the quick answer. Albeit the reasoning surprises me as it would mean I can create views and sort its items any way I want, but I am unable to use the same feature in a formula to display the relevant information. Interesting.  
Thanks again for the help!

---

<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 14, 2024, 8:48am UTC](https://community.fibery.io/t/unable-to-sort-decending/7792/4 "2024-11-14T08:48:19Z")

</div>

We have a feature in the backlog to make collections that are the result of formulas, behave like regular relation fields on the UI (sort, filter, color-code) which will probably solve this

---

<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 14, 2024, 8:48am UTC](https://community.fibery.io/t/unable-to-sort-decending/7792/5 "2024-11-14T08:48:52Z")

</div>

> [@Inconsistent formatting of Collection fields in entity views](https://community.fibery.io/t/inconsistent-formatting-of-collection-fields-in-entity-views/4040):
>
> 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 vis…

---

<div class="post-metadata">

**Author:** ![sternkern](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/sternkern/32/10500_2.png) [@sternkern](https://community.fibery.io/u/sternkern)\
**Post date:** [November 14, 2024, 4:56pm UTC](https://community.fibery.io/t/unable-to-sort-decending/7792/6 "2024-11-14T16:56:23Z")

</div>

That is some great news, I am looking forward to seeing it. Thanks again!

---

<div class="post-metadata">

**Author:** ![helloitse](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/helloitse/32/498_2.png) [@helloitse](https://community.fibery.io/u/helloitse)\
**Post date:** [October 22, 2025, 2:11pm UTC](https://community.fibery.io/t/unable-to-sort-decending/7792/7 "2025-10-22T14:11:00Z")

</div>

Is there a way we can vote on this feature? I notice the original post is a bug report that has come up in several threads now.

---

<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:** [October 22, 2025, 2:37pm UTC](https://community.fibery.io/t/unable-to-sort-decending/7792/8 "2025-10-22T14:37:19Z")

</div>

If you’re encountering the problem described in this topic, then the solution will be supporting normal collection field behaviour for formulas/lookups, which is what is described in the topic mentioned above, so voting on that topic will be enough.
