I’m liking this a lot so far. One issue I’m having is the filters for parameterized pages - I have to write a filter for anything on that page. Is there any way to avoid having to add the filters to everything on the page?

Yeah that’s a fantastic idea. I think there are a couple paths we could go down here: 1. Improve the filter syntax in the templating language so that it’s more natural for analysts (not just a bare js filter expression). e.g. {#where column = $param} 2. And/or filter by default when you have a column name in your SQL query that matches a parameter for the page you are on. I like this, since I think a lot of what people will use parameterized pages for is to build record look ups (e.g. one page per customer) 3. All of the above?

#2 would be great! The customer example is exactly what i'm expecting to build with this. #1 would be helpful since I don't really have a javascript background. So I guess what I'm saying is I like #3 - thanks!

we would definitely need a way to break out of that behaviour