[GH-ISSUE #6651] [FR] linked views should be hidden instead of auto added to the original database #2931

New issue

Closed

opened 2026-03-23 21:26:14 +00:00 by mirror · 2 comments

mirror commented

2026-03-23 21:26:14 +00:00

Owner

Originally created by @annieappflowy on GitHub (Oct 29, 2024).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/6651

Originally assigned to: @appflowy on GitHub.

Description

One thing that’s a bit frustrating is when I have a main grid called 'Tasks' where I manage all my tasks. Every time I link this grid inside, for example, a document, a new view is automatically added to my main grid. This becomes a problem because if I link the Task grid to, say, 50 different documents, I end up with 50 new views in my main grid, making it unusable. If I try to remove these views from the main grid, it also removes the linked grid from the documents. Is there any way to prevent this from happening?

Impact

Database users

Additional Context

No response

Originally created by @annieappflowy on GitHub (Oct 29, 2024). Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/6651 Originally assigned to: @appflowy on GitHub. ### Description One thing that’s a bit frustrating is when I have a main grid called 'Tasks' where I manage all my tasks. Every time I link this grid inside, for example, a document, a new view is automatically added to my main grid. This becomes a problem because if I link the Task grid to, say, 50 different documents, I end up with 50 new views in my main grid, making it unusable. If I try to remove these views from the main grid, it also removes the linked grid from the documents. Is there any way to prevent this from happening? ### Impact Database users ### Additional Context _No response_

mirror

2026-03-23 21:26:14 +00:00

closed this issue
added the
Q4 25

database

new feature
labels

mirror commented

2026-03-23 21:26:14 +00:00

Author

Owner

@bigoh1 commented on GitHub (Nov 6, 2024):

First of all, let me express my sincere thanks to all AppFlowy maintainers!

I can second this issue. Let me give some additional motivation.

In PARA method, one aims to have a central place to store all of your

Projects
Notes
Resources
Tasks
...

and then create relations between them.

Let me illustrate it with an example. Imagine you have two projects:

a) Open a restaurant
b) Open a coffee shop

And in both cases you'd like to store somewhere in your (personal) knowledge management system, the greatest coffee recipe on the planet. You will use it in both projects, so how to apply the programmer's DRY here?

You could probably just create a dedicated page with the recipe in one project, and add a link to it in the other.
Or, you could create one database for your Projects and one for Notes, and in every project display the associated Notes to that project

Why is 2 much better than 1? You can now use the full power of the databases:

Create a field called 'Archived' in your notes DB, and display only notes with that field unchecked
Or create 'progress' field for a note
Or 'starred'
And whatever you want!

This approach can also be applied to tasks.
Create a main DB for all of your tasks and have a relation in them pointing to the projects they are assigned to

This way, you can see all of your current tasks in the main view (say on your home page) and also see tasks per project.

And all of those involve creating many many views. Specifically, each project (you might have 20+ of those) will have a dedicated view for Notes DB, Tasks DB, Resource DB etc

@bigoh1 commented on GitHub (Nov 6, 2024): First of all, let me express my sincere thanks to all AppFlowy maintainers! I can second this issue. Let me give some additional motivation. In PARA method, one aims to have a central place to store _all_ of your - Projects - Notes - Resources - Tasks - ... and then create _relations_ between them. Let me illustrate it with an example. Imagine you have two projects: - a) Open a restaurant - b) Open a coffee shop And in both cases you'd like to store somewhere in your (personal) knowledge management system, the greatest coffee recipe on the planet. You will use it in both projects, so how to apply the programmer's DRY here? 1. You could probably just create a dedicated page with the recipe in one project, and add a link to it in the other. 2. Or, you could create one database for your Projects and one for Notes, and in every project display the associated Notes to that project Why is 2 much better than 1? You can now use the full power of the databases: - Create a field called 'Archived' in your notes DB, and display only notes with that field unchecked - Or create 'progress' field for a note - Or 'starred' - And whatever you want! This approach can also be applied to tasks. Create a main DB for all of your tasks and have a relation in them pointing to the projects they are assigned to This way, you can see all of your current tasks in the main view (say on your home page) and also see tasks per project. And all of those involve creating many many views. Specifically, each project (you might have 20+ of those) will have a dedicated view for Notes DB, Tasks DB, Resource DB etc

mirror commented

2026-03-23 21:26:14 +00:00

Author

Owner

@annieappflowy commented on GitHub (Dec 18, 2025):

Supported in the upcoming release (v0.10.7)

@annieappflowy commented on GitHub (Dec 18, 2025): Supported in the upcoming release (v0.10.7)

mirror referenced this issue

2026-03-23 22:18:56 +00:00

[PR #2931] [MERGED] chore: restore default vscode build task #5483