Report Table Parameters?

My Named Query works, three parameters (default start and end parameters and a string parameter). This all works fine as tested in the named query browser, but I would like to have multiple tables each passing a different string parameter to that one named query. Is this possible? I would imagine through scripting instead of a named query but I'm an SQL guy so I'm stuck in my ways.

You can use a Query String parameter (uses curly braces instead of a colon prefix) instead of a Value parameter. But be aware that if your table name comes from client input, you have opened a huge security hole (aka "SQL Injection").

Yep I have it set up now as a QueryString parameter, and that works (in the Named Query browser). But that's report-wide as I see it is it not? I want to adjust the value of that parameter for separate tables within that report. Basically every table would be "hardcoded" with a different string. This will be an automated report, no client interaction whatsoever but I hear you on the SQL injection concerns. Thank you!

And to clarify, I know what I want to do can be done by eliminating that parameter and using separate Named Queries with those strings "hardcoded". I'm just trying to find best practice for this and I would think one parameterized query would be it.

No, you should be able to set it separately for each query binding in the report.

I think that's where my disconnect is. I don't even see "bindings" like I would see in the Perspective module. I see where my table needs the "Data Key" which I have pointed to what it is for that Query Data Source. But I see nowhere in the table Property Inspector to define the parameter value. I know it must be pilot error on my part.

It isn't in the property inspector. It in the data sources tab. You will need a separate data source (key) for each table. The parameters for your NQ are provided on the data sources tab.

Thanks, got that part. Now off to figure out how to not get tables to collide. Coming from the Iconics ecosystem, I won't say this is worse or better, but I will say it's different.