# Views are a little confusing right now

**URL:** <https://community.fibery.io/t/views-are-a-little-confusing-right-now/9421>\
**Category:** Misc\
**Created:** [August 19, 2025, 9:45am UTC](https://community.fibery.io/t/views-are-a-little-confusing-right-now/9421 "2025-08-19T09:45:51Z")\
**Posts on this page:** 7\
**Page:** 2

<div class="post-metadata">

**Author:** ![danielbmarsh](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/danielbmarsh/32/13104_2.png) [@danielbmarsh](https://community.fibery.io/u/danielbmarsh)\
**Post date:** [August 20, 2025, 3:27pm UTC](https://community.fibery.io/t/views-are-a-little-confusing-right-now/9421/21 "2025-08-20T15:27:53Z")

</div>

Cool discussion. Let me see if I understand this correctly:  
Sometimes there is a need to duplicate a view a variable number of times each with a specific context. Also we need this to all display on one page.

In your example you need a calendar duplicated many times over (one for each client).

If I understood that correctly then I recall a similar idea was discussed here:  
Yuri calls it **Dashboard Card Stream**

> [@Collection Field Layout Mode: Dashboard Card Stream](https://community.fibery.io/t/collection-field-layout-mode-dashboard-card-stream/9214/1):
>
> “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.

For your use case, adding this Card/View Stream to dashboards would solve this issue.

This configuration would look like the following:

- You would have a single dashboard titled “Client Calendars”
- On that dashboard you would add a Card/View Stream that would display a calendar view
- The stream would be set up to have one calendar view per client (set as a context filter)

Does that accomplish this need? If that is the case this might be a Dashboard enhancement instead of a view enhancement.

---

<div class="post-metadata">

**Author:** ![RonMakesSystems](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ronmakessystems/32/14122_2.png) [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\
**Post date:** [August 20, 2025, 7:26pm UTC](https://community.fibery.io/t/views-are-a-little-confusing-right-now/9421/22 "2025-08-20T19:26:28Z")

</div>

Hmm yes, it’s indeed similar.

But why limit it to dashboards?

Currently you can not have a dashboard in a Relation View, so I don’t think Yuri was reffering to the term Dashboard in the Fibery sense when I look at his sketches (which are lovely, btw @Yuri_BC !!)

This is essentially adding Context Views INTO other views. So per entity in this view, I can can a view inside it. This would indeed also solve the problem, with a bit of a different approach. Drilling down instead of up. Also a possibility.

Will explain difference for clarity (using Task Calendar per Client as an example):

Above I suggested:

1. Create Top Level View of Task calender
2. Add Filter and Set it to “Context Filter”
3. This will then make tabs using that field’s entities.
4. These tabs can also be filtered
5. Ability to convert the tabs into sections

What Yuri and Daniel are saying:

1. Create a List view with Clients
2. Toggle a mode somewhere to allow the new layout
3. Create context views inside each Client here.
4. These can be mirrored to show in all clients.  
Making smart folder into a smart view so to speak.

@Yuri_BC @danielbmarsh Did i understand that right?

---

<div class="post-metadata">

**Author:** ![danielbmarsh](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/danielbmarsh/32/13104_2.png) [@danielbmarsh](https://community.fibery.io/u/danielbmarsh)\
**Post date:** [August 20, 2025, 9:59pm UTC](https://community.fibery.io/t/views-are-a-little-confusing-right-now/9421/23 "2025-08-20T21:59:06Z")

</div>

> [@RonMakesSystems](#):
>
> But why limit it to dashboards?

To me dashboards seams like the place to consume multiple views. So if you wanted a view with multiple calendars you could have that. In addition to this, if dashboards can be placed inside entities then you can have the context of the entity.

Yuri’s idea, I believe, allows for adding a widget on the dashboard that is repeatable similarly to how smart folders repeat entities. Except the widget could be a view or some other defined UI.

My concept is simply to allow other views to be defined inside an entity with the context of that entity being applied. These views would be their own separate tab and behave just like smart folder views that also take on the context of their parent.

I like your idea of expanding quick filters. There is a lot that could be added there, like adding inputs or using dropdowns, Airbnb has some cool UI for filters. If you could define filters like that on a view it might help to accomplish what you are after.

Or as I think you are envisioning, you would like to have tabs on a view that switches context similarly to how reports work. Is that right?

Either way, expanding quick filters would be awesome.

---

<div class="post-metadata">

**Author:** ![RonMakesSystems](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ronmakessystems/32/14122_2.png) [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\
**Post date:** [August 21, 2025, 7:06am UTC](https://community.fibery.io/t/views-are-a-little-confusing-right-now/9421/24 "2025-08-21T07:06:48Z")

</div>

> [@danielbmarsh](#):
>
> To me dashboards seams like the place to consume multiple views. So if you wanted a view with multiple calendars you could have that. In addition to this, if dashboards can be placed inside entities then you can have the context of the entity.

This kind of makes sense, but see this: [What if entity view was treated as a dashboard?](https://community.fibery.io/t/what-if-entity-view-was-treated-as-a-dashboard/8322)

The new “Dashboard” view I feel is very artificial when what we really need is for an entity to feel more like a dashboard.

Why place a dashboard inside an entity when you can just make the entity view into a dashboard? I feel like its a much more elegant solution.

> [@danielbmarsh](#):
>
> Or as I think you are envisioning, you would like to have tabs on a view that switches context similarly to how reports work. Is that right?

The main thing I’m trying to avoid is needing to adjust Schema and Filters after the system is set up. The tabs like in reports need to be set up manually, this means making a new tab every time theres a new client, for example. I was suggesting for there to be a way to have “Smart Tabs” kind of.

---

<div class="post-metadata">

**Author:** ![interr0bangr](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/interr0bangr/32/8089_2.png) [@interr0bangr](https://community.fibery.io/u/interr0bangr)\
**Post date:** [August 21, 2025, 1:12pm UTC](https://community.fibery.io/t/views-are-a-little-confusing-right-now/9421/25 "2025-08-21T13:12:56Z")

</div>

> [@RonMakesSystems](#):
>
> The new “Dashboard” view I feel is very artificial when what we really need is for an entity to feel more like a dashboard.
> 
> Why place a dashboard inside an entity when you can just make the entity view into a dashboard? I feel like its a much more elegant solution.

Couldn’t agree with this more!

---

<div class="post-metadata">

**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\
**Post date:** [August 21, 2025, 1:15pm UTC](https://community.fibery.io/t/views-are-a-little-confusing-right-now/9421/26 "2025-08-21T13:15:48Z")

</div>

> [@RonMakesSystems](#):
>
> The new “Dashboard” view I feel is very artificial when what we really need is for an entity to feel more like a dashboard.

this is quite hard to do and will demand a lot of effort. I hope we will get to it next year

---

<div class="post-metadata">

**Author:** ![RonMakesSystems](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ronmakessystems/32/14122_2.png) [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\
**Post date:** [September 29, 2025, 6:07pm UTC](https://community.fibery.io/t/views-are-a-little-confusing-right-now/9421/27 "2025-09-29T18:07:27Z")

</div>

> [@Chr1sG](#):
>
> Weird. I just tried and could embed any smart folder view, including mirrored ones.

@Chr1sG Can you show this working? I’m unable to replicate…

I get this error:

 ![Screenshot 2025-09-29 at 19.09.07](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/4/45bea8615bc97a27f0f3cda6a18bcaf3def1e75f.png)

To reproduce:

1. Make a smart folder
2. Make a view inside an entity
3. Embed it somewhere
4. Mirror the view

[Previous page](https://community.fibery.io/t/views-are-a-little-confusing-right-now/9421.md?page=1)
