Can embedded views have independent filters (not affecting the original view)?

Get Help
1

Hi all,

I have Prompt Database and Playbooks Database. I created a view for the prompts.

I’m embedding a view from my Prompt database into several Playbook pages. Each prompt is linked to a playbook via a relation field.

The goal:
I want to reuse one view and embed it in multiple playbooks, each time showing only the prompts related to that specific playbook.

The issue:
When I add a filter to the embedded view, it also updates the original view used elsewhere. So I can’t apply a playbook-specific filter without affecting other playbooks using the same view.

Question:
Is there a way to make filters local to the embedded view, so I can reuse a single view across different playbooks — each with a different filter? Or is there a workaround that achieves this kind of dynamic filtering?

Thanks for any tips or examples!

2

I’d love that too, but as far as I can tell, the only option is to make pinned filters.

This has my vote for being added to the roadmap. :slightly_smiling_face:

1 Like
3

I’m wondering why you are using an embedded view and not making a relation view (which will have the necessary context filter)?

4

Thanks for your response!

I actually tried going with the relation view approach, but I ran into a limitation — I couldn’t move or drag the relation field anywhere in the rich text area of the playbook. Since some prompts are part of the actual playbook instructions, it would be ideal to position the view exactly where it fits best within the content.

That said, I ended up finding a workaround using smart folders, which solved the issue. Appreciate your suggestion!

1 Like