Yuri_BC
December 12, 2025, 1:19pm
4
The List View “Show All” button should not exist at all, it is a major tension with list views.
1: Preference toggle: “Default to Show All for this view/widget” (persisted per user/per view). This is exactly what multiple users requested after being surprised repeatedly.2: Honest completeness indicators: Always show “Showing 15 of N” (or “partial”) and make search clearly scoped (“search in loaded” vs “search in all”). The search complaint shows why this matters.3: Real lazy loading: Replace “Show all” with infinite scroll / page chunking, but only if they also guarantee correctness for filters, grouping, and search across unloaded items—otherwise it just moves the confusion around.
Directy related issues:
There doesn’t appear to be a way to se the rules of what gets filtered out when Fibery decides there are too many entities to render and the view all option appears.
This has become a thorn in my side for the past week. I somewhat understand the calendar view doing this but list views? This view of tasks for a user shows tasks grouped by status and it initially only showed done tasks.
I’d hope that list views, like table views, don’t automatically filter records.
[image]
Issue:
In a list view, when you use search, you assume it searches all items in the collection. But it currently does not, when you do not first click Show all xx.
The feature that causes the problem: default truncation and the Show All button
There are various long standing issues around List View. The core issue is the way List Views are truncating the output with the Show All button (which is tucked away out of sight) and that as good as ALWAYS requires a user click (if they notice it in t…
I find this severe enough to post it as issue.
Current behavior:
List views are by default ‘truncated’ to show a limited amount of entities.
With more than x items, a button at the bottom shows ‘Show all xx’
Problem case:
When entities are nested in a list view, the list is truncated in an unexpected way:
The truncation does not take into account the nesting and top level entities in the nesting.
For example:
[image]
The nested list actually has multiple top level entities, but only on…
This issue isn’t exactly a bug, but it can confuse new users. Even as an experienced Fibery user I often get confused. The default setting for embedded views, such as a relationship collection field, doesn’t display all entities, presumably to improve performance. This results in nested entity trees showing only partially, with some branches appearing incomplete. Users naturally expect to see a full list of items, but it’s less intuitive when a tree view seems to randomly omit entities. This con…
1 Like