Glad it works for you. One thing I should have mentioned is, that I haven't tested whether the user actually has to hit "Apply" on the first page, or whether they can just hit "Next". It seems like the buttons appear in the wrong order if they have to hit both.

This icon will insert a page break in your prompt" The prompt will then look like this: When the user makes a selection, they must click on "Apply", then "Next". They'll see your second page: A variable set on the first page will pass to the second page.

You can use a single dashboard prompt that is separated into two pages. Set the value of P_Q1 on the first page, and use that value in the SQL of the second page prompt. When the user hits "Apply", then "Next" on the first page, the value of P_Q1 will be passed to the second page.

Also, this happens when an un-aggregated measure is placed in the prompt area. If you go into the column formula and check the "Treat as an attribute" box at the bottom of the window, it will fix it.

I'm not sure why none of the "show data as" options didn't work, but you can do it by creating a 3 "New Calculated Items" on Gender. The calc would be 100*'Female'/('Female'+'Male'+'Not Declared'), with the same for the other genders. Then, go into the Gender column properties and create a conditional data format for when…

If your receiving prompt is a simple column prompt, and your filter is an "is prompted", it won't work with a union that has different formula in the Category fields. If your receiving prompt creates a presentation variable, and your target query filters on that presentation variable, it should work.

Click the "Convert to SQL" box, then edit it to try Joel's solution. Another syntax that works in some filters is @{dashboard.variables['pv_category']}. I've had to use that in Chrome for some situations.

@Johan (South Africa) An alternative to caching NULLs is to use a union query in which the second leg of the union simply returns all possible combinations of the necessary dimensions, with null or zero in the measures column. Then, combine the rows in a pivot or add a results column that combines the values.

The value passed by your prompt will look like 2018,2019. You'll have to parse it and cast as an integer or leave as text, depending on your need. first value: CAST(LEFT('@{dashboard.variables['presvar']}',POSITION(',' IN '@{dashboard.variables['presvar']}')-1) as INTEGER) second value:…

I hope I'm not being pedantic, but @{presvar}{default value} is how you specify a default value for your presentation variable. I only say that because I don't think of that as "concatenating the two". My only remaining suggestion to try is the alternate syntax for a presentation variable that seems to work in some…

I'm just throwing out ideas here, but can you use @{pv_FileName}{"ReportTable"."FileName"} instead of the IFNULL statement? If pv_FileName is being correctly populated by the prompt, how is it ever null?

Hi Dennis, If there are any pivot tables involved, have you placed any aggregation-related columns in the EXCLUDE area? I know that has generated that error for me in the past. Jerry

It looks like you already have it there, but I'm a bit confused by this line in your question: "Gross sales - Invoice amount". If that is meant to be "Gross Sales = Invoice amount", then your formula would look something like: "Your table"."Invoice amt"/SUM("Your table"."Invoice amt" by CASE WHEN "Inventory…

The agency I work for decided to maintain the 11G look and feel. It's the enterprise-wide default at this time, for better or worse. Have you seen skin/style cause issues like this before?

Do you have to use server functions in the RPD? There is no LEFT fnx, and the SUBSTR fnx doesn't use the "from/for" syntax. The equivalent of LEFT('xxxxxx', 3) is SUBSTR('xxxxxx',1,3).

Just to re-confirm, I can't achieve this on a Table view. I can only do it in a Pivot Table view.

That's why I almost always work in pivot tables for tabular results. Pivot tables have much greater flexibility in formatting and cosmetic treatments. I'm off til Monday, but I'll take a look at doing this with a table view then. Jerry

If you use your Grade values to Define pivot table Sections, you can place a duplicate column on the left end of your Rows. Do a Subtotal on it and hide the column. In the example below, I formatted the Subtotal label as shown at right, below.

Did you try this?

Format each subtotal and total label with "@ Total" it will appear as you described.