There's no need to create multiple compound views. You can simply place a table view in one section, a pivot chart view in another, etc. Each section will show the same No Data message.

Hi Dennis, It sounds terribly redundant, but if you're talking about a dashboard page, you can put each separate view in its own section. Your "No Data" message will appear in each section. I don't know of any way to do that within a compound view. Jerry

It's just a running aggregate function. RSUM("Job Applications"). If that column is text, you'll have to cast it as a number.

I don't fully understand your data or the requirement, but this may work: My "Delta" column is equivalent to your "Job Applications" column. By doing a running sum on that column, it provides a basis for MIN(Archive Date by RSUM). At each "0" in the Delta column the last column shows the date of the previous "1". "RSUM"…

Is there more to it than CASE WHEN "Your 6 Mos. Application Count">0 THEN MAX(Application Date) ELSE cast(null as Date) END?

Rather than using the "%" wildcard, you could enter a custom value of "Rows 1-10" in your prompt, then in your query filter: 'Rows 1-10'='@{PV_RN}{xxx}' AND RCOUNT(column)<=10 OR RCOUNT(column)=@{PV_RN}{xxx}

I tried this with a CSV field of my own. The query responds correctly to this filter: I built a dashboard prompt with checkbox options, using a variable prompt, and it works: I was mistaken about the need to include the "['@']" format modifier. In fact, it prevented the filter from working. I hope this helps. Jerry

Your statement is testing a set of "PNumb"s against a set of conditions and extracting a specific date based on those conditions. That looks like the output is one date per "PNumb". There must be more to it if you want to then group by PNumb. Not enough information for me to understand your requirement.

I don't know the details of your data, but I was talking about something like this: CASE WHEN "Details"."PNumb" = "Details"."PI" AND ("JOB"." Name" LIKE '%-DIE' OR "JOB"." Name" LIKE '%-DEW') THEN MAX("XX"."Date" by "Details"."PNumb") WHEN "Details"."PNumb" = "Details"."PI" THEN "XX"."Date" ELSE cast(NULL as DATE) END Your…

Hi ForSly, For any given record, "JOB"." Name" will always equal "JOB"."Name", so your WHEN and ELSE conditions are identical. (Or is that leading blank space intentional? If so, read on.) The first condition will always catch anything that the ELSE statement is intended to catch, since both contain "Details"."PNumb" =…

Hi Chris, I haven't done this, but what I might try looks like this, without using EVALUATE: When you use this syntax: @{param__ms}{item1,item7}, the value passed to the filter looks like this: 'item1','item7'. I'm wondering if you can replace the comma in that result with '||%'. Then, you can nest that result between…

I understand your point and don't disagree. But, I have occasionally created "fake measures" as the OP called them, such as Max(Order Priority by Order#) in order to take advantage of the greater formatting flexibility that a pivot has over a table.

Hi Christian, (and Gianni, Joel), It sounds like he's producing a pivot table. Setting the aggregation to None in a pivot table has always made my data disappear, too. For me, it only works as you describe in a Table view. Jerry

Glad to hear it! Would you mind marking my answer correct, if that's the case? Jerry

You could place a condition on each section of a dashboard that will only open the section if the prompt is not null. The condition can be a simple query with no default value that uses the same prompt. If the prompt is null and the row count for your condition query is 0, the section won't open

Exactly who I had in mind. You stalk us work-around-ers.

I haven't read why you are using a dashboard-scoped prompt if all the subsequent pages have their own date prompts. Perhaps, rather than use a dashboard-level prompt on page 1, you can make that a page-level prompt? From what I've read above, on pages 2, 3, 4, you want to exclude any Customer IDs in the pg1 results, which…

I don't completely understand your requirements, but I believe that setting the value of a presentation variable can still only be done with a prompt. It seems like there are a number of ways to do what you've described, such as using a sub-query filter, or hiding a second prompt in the page's dashboard properties.

If you set separate presentation variables with your page prompts and filter your analyses on them, the unwanted cross-page interaction will stop. I'm not sure how that fits with your "page # 4 analysis invokes an analysis from page level # 2" interaction, however.

Does your target page hold another OBI analysis? The action link would only require that the target be filtered on "Project ID". In this example, I've got an action link on "Title" that sends "PIN" to another page. The target page is filtered on PIN, but PIN isn't required in the output. Am I missing your point? The Action…