Collection Field Layout Mode: Dashboard Card Stream

[Yuri_BC]

Introduction

A new “Dashboard Card Stream field layout mode” upgrades classic collection fields by swapping tabbed views for a scrollable stream of widgetized cards. This is delivers dynamic insights for project managers etc.

Below you see three setups:

1. Classic setup: how a collection field currently is.
2. Collection field displayed with field layout mode ‘Dashboard Card Stream’. This is the key new feature.
3. Optional, but recommeded is to combine that new feature with a parent database to display Dasboard Cards of different departments, teams, etc. This is useful for complete overview and insight (e.g. project managers)

Limitations of Classic Collection Fields and Dashboard Integration Need

Classic collection fields (e.g., “Tasks” in a Project) rely on tabbed views (List in Tab 1, Board in Tab 2), requiring switching and lacking unified overviews. Filters are contextual or global, but no dynamic widgets.
The new Dashboard feature (experimental July 10, 2025) enables widget canvases for views/reports, but it’s sidebar-bound and not entity-integrated—needing embedding in entities for better workflows like project management.

Why New Collection Field Layout Mode

“Dashboard Card Stream” mode replaces tabs with a scrollable card stream, each showing a widget canvas (e.g., List/Timeline View Widget), auto-filtered by parent (e.g., Project). Lazy-loaded for performance, it provides at-a-glance insights within the entity detail page.

Optional Setup B for Flexibility

Use any database as “parent entities” (no new development) to organize cards/widgets meaningfully. E.g., “DashboardHub” DB with entities like “Development”/“Marketing,” each with “Tasks” in Dashboard Card Stream mode, chaining filters (Tasks > DashboardHub > Project).

Purpose and Motivation

Both deliver direct overviews for project managers, reducing navigation for quick decisions. Development motivation: Enables holistic insights in complex projects.

Use Case: Product Launch Project

1. Without Extra Database: Project’s “Tasks” in Dashboard Card Stream streams Task cards with widgets (List for backlog, Timeline for deadlines), filtered to Project. Manager scrolls for aggregated task oversight—ideal for simple projects spotting delays.
2. With Parent Database (DashboardHub): “DashboardHub” DB with “Development” (Kanban for code tasks, Timeline for sprints) and “Marketing” (Table for campaigns, Pie Chart for budget). Project’s “DashboardHubs” in Dashboard Card Stream streams these as cards, nesting Tasks in the same mode. Manager scrolls for team-specific breakdowns—perfect for complex projects with segmented views.

[danielbmarsh]

Why completely replace tabs instead of making one of the tabs this view? I think multiple entity views is still valuable even with this feature request.

My proposal is to allow for all types of views to be added on entities (not just field layout views):

Add Views to Entities

Sometimes I am on an Entity view that has a lot of related data. And that related data should be more prominent to the entity. Example: On an Account, you may want a view dedicated to Contacts, support requests, orders, etc. Instead of this relation being buried on the page, it should be full page and potentially a pinned view to make it quicker to access. Fibery can already expand these views to full screen: [image] [image] So this would be more about taking this and pinning it as a v…

If a Dashboard view could be added to an entity, could enhance dashboards accomplish your goal?

From what I can tell dashboards on entities would need the following:

• Context Filtering for dashboards which would pass down to context filtering for cards
• Repeatable widgets based on entities linked to the entity. This would programmatically repeat widgets within the context of the entity.

Am I close to catching your vision?