I’m working with ClearQuest and need some help with SQL queries. When I create queries through the Query Wizard, I can easily set up filters that ask users to enter values when they run the query. This works great for basic queries. But when I switch to the SQL Editor to write more complex queries or customize the SQL code, I lose this dynamic filtering feature. The query becomes static and doesn’t prompt users for input anymore. Is there a way to keep the user prompt functionality while still using custom SQL in the SQL Editor? I want to be able to write my own SQL statements but still have the query ask users for specific field values when they execute it.
here’s another trick: use named parameters with :parameter_name syntax in your sql. way more readable than question marks scattered everywhere. clearquest still shows the input dialog, but you’ll get better labels. pro tip - test ur query with hardcoded values first, then add parameters. makes debugging much easier when stuff breaks.
You can make dynamic prompts in ClearQuest SQL Editor using parameter placeholders. Just swap specific values in your WHERE clauses with question marks. So instead of WHERE field_name = 'specific_value', write WHERE field_name = ?. ClearQuest will prompt users for values when they run the query, following the order of your question marks. I use this all the time for complex reports that need custom joins or advanced filtering - stuff the Query Wizard can’t handle. Works great with LIKE operators too for partial matches.