Thanks again, Ram. Clearly, I'm not the first to find this annoying.

Hi Ram, Thanks for the quick reply. That closed state you describe only persists if I close them all before logging out each time. I work in many dashboards all day, so this is a step I'd avoid, if possible. If we had a smooth scroll, rather than the one-line-at-a-time arrow button, it would be a lot better. The Favorites…

Thanks, Marcelo. I'll do that. If I'm the only "sufferer" in this situation, this idea can be removed. Jerry

+1 for this idea.

If you don't have double columns enabled, you can create a variable prompt based on your concatenation. Say your prompt produces a presentation variable "varConcat", with a value like CityCode||' - '||CityName, say "13 - Rome". The analysis can be filtered like: CityCode=Left('@{varConcat}{xxx}',2)

Hi Indra, I have done this on a dashboard, but not on a stand-alone analysis. I needed 4 column headings for year1, year1+1 year1+2, and year1+3. I have a repository variable for year1 (called "STIPYear1"). I created a hidden dashboard prompt that creates 3 presentation variables: varSTIPYear2, varSTIPYear3, and…

Just commenting to reinforce all of the above comments. Presentation variables are used throughout our existing dashboards. We won't be getting much use out of DV until PVs can be used in them.

Hi @Steelbird , Sorry - I'm rarely on here now. If you still need this, leave the customer name in the data, and use a pivot table for your summary. Set the agg rule to max on your rank columns. Data, using your formulas, with pivot table below:

You are showing it in a column editor window. It goes into a filter in the criteria tab. Here's a two-column query, to be filtered on Employee Last Name: Select "Filter", then "Convert to SQL":" Enter the filter in the "Advanced SQL Editor" window: My prompt looks like this: My results look like this: A slightly more…

In the filter of the query that you are prompting.

I just wrote a long response which disappeared when I hit the "post comment" button. aargh. You should read up on PVs, they add tremendous flexibility in your dashboard prompts. In your case, create a variable prompt (you'll see that option when you select the green plus sign). Name your variable and select user input and…

Is your prompt in the query itself or is it in a dashboard prompt? Let's assume a dashboard prompt. Choose "Variable Prompt": Name your variable, user input and data type. (also add a default value, if you want: Generally, Presentation Variables are referenced like this: @{varSupplier}{'default value'}, or…

Use the prompt to initialize a presentation variable, say, varSupplier. They can enter a value in upper or lower case. In your query, use a filter like this: UPPER('@{varSupplier}{xxx}')=UPPER("Bidder"."Supplier Name") This way, their prompt entry and the filtered column are both tested in upper case. I've used this many…

If you insert a page break between prompts 2 and 3, The first two prompts are submitted when "Next" is selected to go to Prompts 3 and 4.

You may have several issues here. One is that you are using both the CAST and TO_CHAR functions for the same purpose. Pick one. You also may not have access to the EVALUATE function, depending on your system, but there is no detail in those error messages, so I don't know about that. I would start by creating a column that…

You can only concatenate text fields. If CAST( XXXX TO DATE) doesn't do it, you can use EVALUATE with the TO_CHAR function to get your specific format.

Try adding a "By" clause to your calculation:

Try checking off the "Treat as Attribute" box in the "Edit Formula" window.

If your prompt populates a presentation variable, say "varAcct", you can filter your query on "tablename"."Account Number" =LEFT('@{varAcct}',14) But, this solution doesn't address all the other potential typos that may occur when users are typing in a 14 digit number.

The people in question need to be identified in the data itself. That way, the "Deliver Relevant Rows" option can be selected.