Filter a view based on connected field in ACCOUNTS table

[LeighBerrell]

I'm trying to find a way to create a "universal filter" across multiple pages in an app. For example, to allow a user to select a specific project, and no matter what page they go to the views on those pages are all filtered to just show records connected that project. My idea was to have a field in the ACCOUNTS table , connection to PROJECTS, and give user a modal screen to select their target project. That project name could be loaded into a memory variable. Then every time a grid or other view that has an appropriate KTL keyword assigned, KTL filters that view using the target project. I don't think there is a way to achieve this with KTL now (but happy to be corrected), but I think it would be great for users to be able to limit their focus this way. Thoughts?

[cortexrd]

Hi Leigh,

This would be an interesting feature. But not easy to implement, especially with all the special cases, where you'd have a combination of filter parameters including that project field. We'd have to "merge" the filter with the current one, if any. And a lot of other corner cases.

Besides you, I'm not convinced that many users would need this.

If that's very important to you and has a lot of value, send me an email and we'll discuss the options.

Norm

[LeighBerrell]

I find a way to do a simple one field global filter using page rules and it works for what I need. Rgds Leigh Berrell

…

________________________________ From: "Cortex R&D Inc." ***@***.***> Sent: Saturday, 4 April 2026 12:44 am To: cortexrd/Knack-Toolkit-Library Cc: LeighBerrell; Author Subject: Re: [cortexrd/Knack-Toolkit-Library] Filter a view based on connected field in ACCOUNTS table (Discussion #600) Hi Leigh, This would be an interesting feature. But not easy to implement, especially with all the special cases, where you'd have a combination of filter parameters including that project field. We'd have to "merge" the filter with the current one, if any. And a lot of other corner cases. Besides you, I'm not convinced that many users would need this. If that's very important to you and has a lot of value, send me an email and we'll discuss the options. Norm — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>