Categories
- All Categories
- 15 Oracle Analytics Sharing Center
- 14 Oracle Analytics Lounge
- 213 Oracle Analytics News
- 42 Oracle Analytics Videos
- 15.7K Oracle Analytics Forums
- 6.1K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 78 Oracle Analytics Trainings
- 14 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
OBI Dashboard report differs from analysis based report
Answers
-
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 is to remain filtered on the pg1 prompt. I'm assuming you are using a sub-query filter to exclude the pg1 Cust IDs?
One way to eliminate the cross-prompt interference, and at the risk of drawing the ire of the real expert's , is to use a different date field in the page 2+ date prompts. As long as the data types are consistent (both dates or both timestamps), and you are using presentation variables, your analyses will respond correctly. The second date field doesn't even have to be from the same subject area. It just has to contain all the dates that you expect to be used in the analysis.
I have used date fields from our financial system, because I know there are transactions every day, in order to prompt for Contract Award Dates in a different model.
A dashboard-level prompt that uses "Finance"."Transaction Date", will not override a second prompt that is using "Contracts"."Award Date".
Naturally, your analyses are filtered on the different pres. var. names, not on the field names.
0 -
0 -
Exactly who I had in mind. You stalk us work-around-ers.
0 -
As long as it's justifyable and not simply "Oh it works so why think further", it's fine.
0 -
Jerry
Thanks for offering your insights...
Yes, I am using sub-query filters to exclude Customers.
The suggestion to use another date column as a filter is not viable based on the current table definition.
However, based on this approach, I may set prompts based on the calendar quarter and year that would be unique to that page in the dashboard.
Another question that I would like to submit...can I suppress the launching of the analysis from the dashboard when I configure the Dashboard date prompt without default values ?
I assumed that omitting default date values would delay the launch of the analysis until the date prompts are populated.
However, the analysis returns all rows in the table based on the other filters without regard to transaction date.
Thanks in advance for any feedback.
0 -
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
0 -
Jerry
Thanks for offering that solution.
I will proceed based on your instructions.
Jim
0 -
Jerry
I was able to implement the condition based on your instructions and it worked....thanks.
0 -
Glad to hear it! Would you mind marking my answer correct, if that's the case?
Jerry
0
