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

[Yuri_BC]

@mdubakov

You have a talent…Can we rename Fibery to FrogFarm? or Froggery?

[Hendrik]

@mdubakov

Now you can create Dashboard Views in Fibery and embed other views (and reports) into them.

YES!
THANK YOU!

BUG(?):
In whiteboard, when scaling embedded views in the vertical dimension, the view gets truncated - see image below.

There is also weird behaviour when zooming some embedded view types on whiteboard where the browser gets zoomed instead of the view.

[mdubakov]

@Hendrik

In whiteboard, when scaling embedded views in the vertical dimension, the view gets truncated - see image below.

It is known issue and it will be fixed in Whiteboard soon.

[Hendrik]

@mdubakov

It is known issue and it will be fixed in Whiteboard soon.

Thank you!

---

Also:

1. The timeline view on the dashboard does not have the corner resize tab - pls see below. It is in fact scalable (with careful aiming) but resizing seems to be more erratic than the other views.
2. I also found the weird inadvertent browser zooming behaviour (I use Brave browser) to also be prevalent in the dashboard view.

Thank you guys

[carson]

@mdubakov

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.

Such a nice little addition. Super useful, elegant. Didn’t know I was missing it until I had it.

[AdVhPkgKad]

Very nice, but can we change the height of the map?

[mdubakov]

Are you not happy with the default size?

[Minh_Tri_Do_Hang]

@mdubakov

Dashboard View

@mdubakov

Unlimited self-relations on Gantt View

so fast, thank you for those releases

[AdVhPkgKad]

I think the users (in my organisation) will complain about the size, and not being able to zoom.

Personally, I would just go to the map view

[Alex_Rublev]

I haven’t tried dashboards yet, but it sounds awesome, really important feature

[bear]

Amazing update! Checking out dashboards now! Really cool! And I love the Gantt View, unlimited self-relations are a good improvement for that! And I really wanted to have location fields visible on the entity view, as I often have applications that use the location fields working in geo-it. So, I love that surprise

[Bronn]

@mdubakov

Dashboard View (experimental)

Much love for this! To spice dashboards up even more I’d love to be able to use the “is Me” context filter in reports outside of context views. But maybe I should just use context views more!

@mdubakov

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.

Can we have the 2 new buttons act the same? I’ve setup forms, but if someone clicks the more visible new button on the view, the fields are different and sometimes include fields that are filled in by rules, which causes confusion.

[Yuri_BC]

@mdubakov

Dashboard View (experimental)

I assume that Dashboard Views will become one of the available collection field views, right?
Because we don’t use the left sidebar (as UI design choice) and want everything to happen in contextually filtered views in collection fields (not embedded in rich text fields ).

Examples

• Project Management: A “Tasks” collection in a “Project” entity with a Dashboard View showing a task status pie chart and timeline.
• CRM: A “Deals” collection in a “Client” entity with a Dashboard View of deal stages and interactions.
• Product Development: A “User Stories” collection in a “Feature” entity with a Dashboard View of a Kanban board and priority table.
• Event Planning: A “Venues” collection in an “Event” entity with a Dashboard View of map previews and cost tables.

[Chr1sG]

@Yuri_BC

I assume that Dashboard Views will become one of the available collection field views, right?

Sounds rather like a ‘dashboard layout’ option for entity view (as an alternative to 1- and 2- column layout). This is discussed a few other places in the community.
Or did you really want a dashboard crammed into the space currently available for a single to-many field?

[Yuri_BC]

I would be very happy if it looks like Feed View, such that multiple dashboards can be shown in full feed width and height of each entity and filtered according its collection view filter settings.

For years I have suggested that Feed View has massive potential, IF all field can be included such as collection fields. I understand performance impact but something like lazy loading can take care of that.

So for the Dashboard View as a field, this will likely need a new field type that is fully dedicated to one Dashboard View, similar to the current Rich Text field, but instead of a rich text collaborative document with ID and secret, the Dashboard View would be there with ID and secret.

These two feature improvements (Full Feed View & Dashboard Field) likely open up massive possibilities in fibery.

The same could apply for Whiteboards, which would cover a previous post of me about Whiteboards being fully visible in collection fields feed views (not only as list view item)

Am I making reasonable assumptions? If not, what would be technically the challenge?

[Chr1sG]

Your original request

@Yuri_BC

Dashboard Views will become one of the available collection field views

implies that each entity could potentially have a dashboard option for each to-many relation field, which seems somewhat at odds with the value of dashboard (= a full page canvas in which multiple views can be embedded).

You’re now saying

@Yuri_BC

I would be very happy if it looks like Feed View, such that multiple dashboards can be shown in full feed width and height of each entity

Feed view is a ‘data view’ which shows multiple entities, so your request implies a scrollable view of multiple entities, each of which with a (single) dashboard layout, no?

In other words, if you want dashboard as an option for each relation view (or is itself a new field type) then

• 1 entity view can have multiple dashboards (one per collection field)

whereas if dashboard is a layout option for entity view (an alternative to 1-column or 2-column layout) then

• 1 entity view can have one dashboard layout (although an entity can have multiple entity views)

Of these alternatives, given the flexibility of a dashboard, I am struggling to see the use cases for allowing entity view to accommodate multiple dashboards. I do see the value of dashboard as a layout option.

Note1: Aside from any dashboard discussions, I do see the appeal of a data view which allows users to scroll through entities. The options for layout of each entity can be debated (dashboard, multi-column, etc.) and hence I might refer to this concept as ‘stream view’ to distinguish from the specifics of ‘feed view’, which is specifically focussed on quickly panning through each entity’s contents of a rich text field.

Note2: all of the above is tangential to the situation of the whiteboard collection. Given that there can be multiple whiteboards linked to an entity, it does indeed make sense to develop a better method of viewing these whiteboards than a simple list.

[Hendrik]

@Hendrik

The timeline view on the dashboard does not have the corner resize tab - pls see below. It is in fact scalable (with careful aiming) but resizing seems to be more erratic than the other views.

This seems to be fixed - thank you! The vertical scroll on timeline view seems to disappear though.

Interaction on dashboard view seems to be more stable. That is awesome. I like that I can now scroll the whole page until I click on a widget to give it focus. It would, however, help a lot to have a visual cue for the current accent window/widget though - heavy outline, title bar colour, everything else slightly lighter, etc (?)

Keep polishing this awesome new view type please!

[Yuri_BC]

@Chr1sG

and hence I might refer to this concept as ‘stream view’

Thank you! Based on our discussion and your suggestions, I created this feature request. I’m very interested in your feedback and suggestions:

Collection Field Layout Mode: Dashboard Card Stream - Ideas & Features - Fibery.io Community

[Wilco_Boode]

Hey, any chance that you will allow us to add forms to the Dashboard view as well?
We have a booking system, but the lack of conditional fields forces users to open both the overview as well as the actual booking form. It would be great if we can show these on one page using the dashboards.

[nathan_jay]

@mdubakov

• 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

Dashboards are awesome!

The best example I have come across of how to create dashboards from database charts is Equals.com (I use is most most days). The one unique and super powerful thing they have is the ability to add additional context to the dashboard to improve layout and readability. This is what you can add directly to the dashboard: