December 11, 2025 / Reports performance improvements, View Items Menu unification

[mdubakov]

Mostly bug fixes and improvements in today’s release

View Items Menu unification

To keep database selection menus consistent across views, we’ve updated the ‘Cards’ menu in all View. Same functionality, smoother experience. Enjoy!

Reports performance improvements

Reports in Fibery are, well, not fast. They are especially slow for databases with 50K+ records. The main reason is a combination of records count and amount of fields in a database. In the past, we loaded almost all the fields to simplify report creation, but now we applied a more clever algorithm that loads all fields for small databases, and just some fields for large databases, and that dramatically changes new report creation time (in some cases 10x faster). As a downside, you have to add necessary fields to the reports manually, via Add field action.

Moreover, we trimmed all unused fields in all existing reports in all accounts, it means that most likely your reports will load faster (in some cases 10x faster).

Improvements

• Hierarchical Table or List. Now when you delete the top level of the hierarchy, you don’t lose the things below
• Relation Views: Embedded List View “Show all” was very hard to notice and it caused confusions. We’ve moved it to the left and it should be more visible now.

Fixed Bugs

• Flexible Domain:
  • Database name singularized incorrectly despite being an English word.
• Documents / Rich Text:
  • If you have a block of text pasted in at once with several different links, the whole lot is converted to a single link, and if you click on any of the entries it opens the first link.
  • Markdown with link text is not treated as a link on text paste.
  • Cannot delete callout from rich text if it goes after multiple columns.
• API:
  • Automations: http.post request does not follow redirects in JS action.
  • API Token Management: Hover state is missed for token description.
• Reports: Missing ‘Data’ option for Table Reports.
• Export Data: Wrong column order in the exported csv after adding and re-ordering new fields.
• File Field:
  • File upload hangs if upload several files at a time to the file field.
  • Files uploaded in the random order if drag & drop several files at a time.
  • ‘Download all files’ action should be disabled when no files are uploaded.
  • There should be no jumps and flickering when uploading or removing files.
• Gantt View:
  • Missing names of entities by default.
  • Creating dependencies in Firefox works improperly.
• Timeline View: Can not change dates for card in read-only lane.
• Whiteboard:
  • Fix hover highlight in actions popup and toolbar.
  • Connector Tool: The connector doesn’t duplicate when using Opt (Alt)+Drag with the mouse.
• Board View:
  • Unpleasant blinks on board on moving card.
  • Columns reorder sometimes works improperly on the Board view.
• Automations: “On Schedule” rule runs for deleted database and admins receive notification about failed rule with link to ‘not found’ page,
• Integrations: misleading “Unable to find account” error when integration Account is deleted.

P.S. We’ve also explored how easy it is to create and deploy custom Fibery integrations with AI. It appeared it is relatively easy. Try it for yourself!

[interr0bangr]

@mdubakov

Relation Views: Embedded List View “Show all” was very hard to notice and it caused confusions. We’ve moved it to the left and it should be more visible now.

This is better than it being on the right, but it’s still frustrating that it needs to be there at all sometimes. Could you at least up the limit to 25 entities before the “Show all” prompt displays instead of the current 15? Our teams miss things literally every week because it’s such a low ceiling.

[Yuri_BC]

The List View “Show All” button should not exist at all, it is a major tension with list views.
At least, the following should be in place:

• 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:

Issue: List View is too random and restrictive with "Show All"

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]

List View Search Filter gives no results when Show All is not clicked

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…

List view with multiple databases incorrectly filters output

Working of list views A list view by default displays 15 entities of a certain database, thus 15 rows. When a list view contains multiple databases, the number of rows is multiplied by the number of databases. For example, if a listview has two databases A and B, you see by default 30 rows, 15 entities of database A and 15 entities of database B. Problem When we sort this view by 'All Databases > Creation Date - Descending, we expect a list of entities of databases A and B, which are sorted b…

Misleading truncation of nested entities in list view

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…

Embedded List View "Show all" is very hard to notice and it causes confusion

related: List view with multiple databases incorrectly filters output - Bugs & Issues - Fibery Community and Entities appear ‘missing’ in an entity tree - Bugs & Issues - Fibery Community

Entities appear 'missing' in an entity tree

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…

[mdubakov]

@Yuri_BC

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.

Imagine you have a list of 150 features inside a project. Default Show All is not a good idea then.

@Yuri_BC

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.

This is a good idea, and search in general should always search in all, we will check it, looks like a current bug to me

@Yuri_BC

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.

How it will work? It is not clear what you scroll and it will be a very weird behavior for a user, so not something we will do.

[mdubakov]

We will think, there is indeed a lot of room for improvements. I hope we will address these problems in January

[helloitse]

@mdubakov

Default Show All is not a good idea then.

Why not? They would all show in table view?

Why is the limit so small?

[mdubakov]

@helloitse

Why is the limit so small?

There is no technical problem to increase the limit. We will think about more cohesive UI and ideas how to manage large lists but still provide flexibility for users

[RonMakesSystems]

One idea is to add a “Show First X [Database Name]” in the filter options that can be added across all views. Maybe defaults to 15 in the relation views, but can be changed then by architect.