July 10, 2025 / 🪃 Dashboard View (experimental), Fibery AI (Build mode) is out of experimental, Unlimited self-relations on Gantt View

[mdubakov]

Today’s sunny release contains 30 bug fixes and some small, unexpected and intriguing improvements. Enjoy!

Dashboard View (experimental)

Now you can create Dashboard Views in Fibery and embed other views (and reports) into them. You may wonder what is the difference between Dashboard View and Document?

• Dashboard Views has better layout management. You can easily add views as widgets, resize widgets and drag them around. And it just looks better
• Dashboard View can be a context view, so you can create a single Dashboard View for some Project (in Projects Smart Folder) and enjoy automatic project filter for all embedded views
• Discoverability of Dashboard View is better, it takes some mental power to understand that you can use Document as Dashboard
• It enables future improvements, since we can add new widgets or even allow people to create own widgets in the future

Dashboard View is available in all paid plans, so go ahead and try it.

NOTE: Dashboard View is experimental, so it is a bit rough and not polished yet. You can enable it in Settings → Experimental Lab. Your feedback will make it better!

Fibery AI (Build mode) is out of experimental

We have fixed dozen of bugs and Fibery AI (Build) is ready for all admins to try. It can create new spaces, databases, fields, formulas, relations, Table and Board Views. It can update data in batch and do things that can’t be done with other tools so far.

Unlimited self-relations on Gantt View

We’ve released Gantt View a couple of weeks ago and did a serious mistake — we did not support unlimited self-relation hierarchy. God knows why… Maybe I (as a product owner of this feature) got overwhelmed by context switching, maybe summer heat hit me, who knows. Luckily, this limitation was quickly discovered by the community.

We re-did Gantt View to support this use case. Now you can have nested entities with self-relations any level deep. Gantt View setup was tuned as well to accommodate this change and we tried to safely migrate all existing Gantt Views to this new model.

We also fixed many bugs, so Gantt View should be more enjoyable to use.

NOTE: unlimited self-relations work on Gantt View as a stand-alone View, there are still two-level-max for views created inside entities. It will be fixed soon.

Display Location Fields as pins on a map

You can now display Location fields as map previews directly in the Entity View. Just head to Layout settings, toggle the Location field to Preview, and pick your preferred map style and zoom level.

Whether you’re tracking events, customers, real estate, or anything else tied to a place – this feature helps you see your data in context.

NOTE: Map previews are static – but don’t forget, you can always create an interactive Map View for deeper exploration.

Sync Notion standalone Pages to Fibery Database

Previously, we started to sync and import rich-text content of Notion’s Database Pages into Fibery. Now it’s standalone Pages’ turn:

They are synced into a new Pages DB and their hierarchy is captured via a one-to-many self-relation, so you can visualize them in the sidebar using a Smart Folder.

If you are transitioning from Notion, let us know what’s missing.

Undo/Redo just got better in Whiteboard

We’ve improved how Undo (Ctrl/Cmd + Z) and Redo (Ctrl/Cmd + Shift + Z) work in Whiteboard to make them more consistent, and reliable across all actions. Whether you’re editing, moving, or adding content, you can now easily undo or redo your own changes with confidence.

Improvements

• Table View: now when you have many databases, you will not see dozens of New [Database] buttons, but just a single New button. This changes also went to context menu.

• Integration. Now we do not stop ongoing import when integration services restart. It eliminates some weird problems when you expect some data already, but there is no data at all.

Fixed Bugs

• Gantt View:
  • Self-relations don’t work properly on Gantt view
  • Show week dates as range (Jun 23 - Jun 30) instead of just week start (Jun 23) on timeline when weeks range is selected
  • Secondary dates are not shown if secondary dates card if far away from primary dates card
  • Missing “Create After” action for “group by” rows
• Whiteboard:
  • Undo for lines doesn’t reflect changes made to curves
  • Undo for moved card returns it back to original position but changes position of some other cards
  • Ctrl+z does not undo ‘Multi entity insert’
  • Section does not get restored to the resized version after Undo
  • Lock background: It’s possible to change text in existing objects in section if “Lock all” is selected
  • Lock background: It’s possible to resize, move and even delete section if background is locked
  • Lock background: It’s possible to change section style if background is locked
• Permissions:
  • Extend button is not hidden if User doesn’t have access to child DBs
  • Custom access template is not hidden from selector if User lacks some capabilities
  • User who shared the entity with the Group can’t edit or remove access via Manage Access screen if he doesn’t have unapplyAccess capability to the Entity
  • Wrong calculated capabilities are highlighted for Contributors in Space access audit popup
• AI Agent:
  • Build mode: Improve correctness of State creation as workflow, not single select
  • Build mode: Populate fibery/relation field for enums automatically for agent
  • Build mode: hasLinkRule bug in AI Agent built space
  • Build mode: Agent names enum types incorrectly (not according to naming convention)
  • Build mode: Let agent know about default behaviour of commands
  • Build mode: Agent should not treat Enums as databases (but as a special narrow case)
  • Build mode: Agent should not add UUID and JSON fields
  • Build mode: Disallow to create fields with type fibery/rich-text for agent
  • Build mode: AI can’t group by state if I ask it to on Board View
  • Build mode: Agent creates database outside of any space
  • User Guide Assistant does not work in public user guide
• Search & Recent Items: Searching for system page (for example “csv”) breaks search UI
• Find and merge duplicates: Sometimes view with duplicated values does not get re-created
• Notion integration: Field names collision issues
• Linear Integration: Cycle’s start and end dates might be the same which causes an error
• History & Audit Log: ‘Undefined’ instead of id in warning message

Your warm (and cold) comments are welcome!

[jandrabek]

Dashboards are epic! Love it!

[Renato_Carvalho]

Oh yes!!! Dashboards!

[jandrabek]

Can you replicate dashboard grid behavior for entity views?

[interr0bangr]

Yes, I was hoping to use a dashboard within an entity, basically replacing the complexity of having to manage embedded views within rich text fields. We do 99% of our work within entities themselves so dashboard being treated as the same type of view as whiteboards or documents isn’t particularly useful for us.

[Chr1sG]

‘dashboard’ as a layout option for entity view is a bit harder to implement.

[RonMakesSystems]

@interr0bangr @jandrabek Get your votes in! What if entity view was treated as a dashboard?

Crazy how fast you guys got the dashboard view up in running!! The tech works really nicely. Still I think conceptually it’s not a view, but I’ll provide feedback as it is in the current state.

1. Could we embed entities other than docs?
2. Why do dashboards not allow for split view? Its already responsive! If I have an overview, and im drilling into an entity in that overview, I still want to see the overview. I find this limitation a bit of a weird choice.

Location:
Really cool addition. It’s a bit hard to find the settings for the Map Type and Zoom Level. When changing the “Display as” using the three dots in the entity view rather than the “All fields” menu, it doesn’t show up. In an ideal world it would have the following:

1. Inputtable/Interactable: Allow search and point drop / move point in map. Every time it refreshes, it zooms back to default zoom and on point of address.
2. Allow map to be the display input in forms.
3. Show the address somewhere on the map. Not sure if this is really needed though, as you can always make another formula field with the location name and put it on top of the map view. But if you have a point in the middle of nowhere, its a bit tricky to know what you are looking at.

Lovely stuff!

[Illusory]

I love you guys

That is all for now.

[mkervo]

Dashboard views are awesome, well done !!

FYI: improvments on whiteboard’s CTRL+Z missed the AZERTY keyboard bug. French customers mistakes are permanent

Switch to QWERTY ? Yes ! But don’t hit CTRL+W by mistake… it will close the tab …

[Chr1sG]

@RonMakesSystems

Still I think conceptually it’s not a view

I think this is just semantics. We tend to call ‘entity view’ a view, and we call ‘tables’, ‘boards’, ‘lists’, etc. views, and sometimes people call a ‘whiteboard’ or a ‘document’ a view.
If it avoids ambiguity, just call it a ‘dashboard’

To be fair, it is not in the View submenu.

@RonMakesSystems

Could we embed entities other than docs?

As well as Documents, you can embed boards, lists, tables, whiteboards, reports, etc. but you can’t embed an entity.
If you want to see entities and views at the same time, maybe use a whiteboard.

@RonMakesSystems

Why do dashboards not allow for split view?

Do you mean ‘Why does a dashboard take up the whole screen?’
Some things become less usable/attractive if limited to a single panel, but maybe we should allow it

@RonMakesSystems

If I have an overview, and im drilling into an entity in that overview, I still want to see the overview. I find this limitation a bit of a weird choice.

What do you mean here?
Overview = table view (for example)?
If you’re ‘drilling into an entity’ what does that have to do with a dashboard item (in the sidebar)?

[RonMakesSystems]

@Chr1sG

I think this is just semantics.

I disagree. I think having clear definitions of terms makes things easier to understand in the long run, even if more complex. Once you get it, it clicks and makes sense. Fibery has so many places where you can see how much things were thought out, and things just work and make sense, and are aligned with each other. Document, Whiteboard, and Dashboards (and comments) are not that.

@Chr1sG

As well as Documents, you can embed boards, lists, tables, whiteboards, reports, etc. but you can’t embed an entity.

The reason I ask is for the prep for the documents to database migration. When this changes, this will need to be rethought. Either allow any entity, or allow none (imo)

@Chr1sG

Do you mean ‘Why does a dashboard take up the whole screen?’

Yeah, as in, it starts as full screen like any other view, but when opening an entity to see more details (which is what I meant by drilling down, was indeed unclear sorry), you can no longer see the context of the dashboard.

[Oshyan]

Absolutely huge release, awesome!

[timothy]

" Some things become less usable/attractive if limited to a single panel, but maybe we should allow it "

Enthusiastic vote for this! Love the context of panels and am willing to sacrifice ‘pretty’ to have the context. Another user can just close the dashboard panel if they don’t want it or middle-click (on mouse) to open in a new tab.

[mdubakov]

@timothy

Enthusiastic vote for this! Love the context of panels and am willing to sacrifice ‘pretty’ to have the context.

Dashboard will feel jumpy with panels, since widgets will be resized and it will not feel OK

[Matt_Blais]

Instead of resizing the widgets to fit the smaller panel, could you instead add a horizontal scrollbar to the Dashboard panel?

[RonMakesSystems]

Or maybe quick animations? Generally the flow is:
Full width → Split view. Then you stay here for a while as long as you open other entities from the dashboard.

The shift from full width to split view only really happens once per “Exploration” or “Session”, or however you want to call it.

[Chr1sG]

@RonMakesSystems

I think having clear definitions of terms makes things easier to understand in the long run, even if more complex.

OK, so ‘officially’ (if there is such a thing ) views include ‘data views’ (boards, tables, lists, etc.) and ‘content views’ (documents, whiteboards, and now dashboards).
And ‘Entity View’ is just ‘a view of an entity’ (duh) so tends not to be included under the umbrella of ‘Views’.

So Dashboard is a View, but not a ‘data view’ which is what most people think of when they hear the word.

EDIT: I forgot to mention forms, which are also a kind of view

[Tommy_Hedley]

The dashboard view is pretty cool! I’m just starting to play around with it and I noticed a small bug: if you add a view to the dashboard (I’ve only tried it with reports) and you delete the view elsewhere, you no longer have a way to delete it in the dashboard view.

[mdubakov]

@Tommy_Hedley

you no longer have a way to delete it in the dashboard view.

Yes, we discovered it today, same for context view, if you insert some context view, it will not work and widget will be impossible to delete. We will fix it soon