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 am still troubleshooting an issue where the transaction date prompts defined with page level scope are being overridden by transaction date prompts from another dashboard page.
The prompts all pertain to the same column, 'transaction-date'.
Note that I disabled the browser auto complete feature for forms and searches, but this did not have any impact.
Any suggestions to workaround this issue are appreciated.
0 -
Issue is each of four dashboard pages have a prompt for the same column " transaction date" using a 'between date range.
. All pages are defined with page level scope.
When page # 4 analysis invokes an analysis from page level # 2, the date range from page # 4 is overriding the date range intended for page # 2.
I tried updating the browser option to disable auto complete, but this did not have any impact.
Thanks for any suggestions to workaround this issue.
0 -
Can you explain what is the issue with some screenshots?
What do you mean by "When page # 4 analysis invokes an analysis from page level # 2, the date range from page # 4 is overriding the date range intended for page # 2."? Can you please explain this scenario using some screens? That will be really helpful.
0 -
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.
0 -
I have included two screen captures.
The first screen capture shows an analysis from a dashboard page with the tag "Override" with a date range of 1-1-18 to 3-31-18.
The second screen capture with the tag "Exclusions" is from a later dashboard page that uses a date range of 7-1-17 to 12-31-18 in the analysis.
The Exclusions analysis includes a filter to bypass the customers from the Override step.
Therefore, the Override step is triggered again, but in this instance, it does not use the date ranges defined for that analysis.
The date ranges used in the analysis are 7-1-17 to 12-31-17 instead of 1-1-18 to 3-31-18.
Therefore, I conclude that, for some reason, the "page level" scope is not being enforced.
0 -
Sorry but everything works as designed.
What you were hoping to happen is just impossible ...
Your only chance would be to try what Jerry posted, if the analysis you use as filter works on a different variable you have a chance the context will be preserved once you navigate away from the page. Otherwise it's normal that it doesn't work like that.
Keep in mind that in your "Exclusion" analysis you aren't referencing the "Override" analysis of your dashboard, but the generic "Override" analysis of your catalog which has no filter sets. Therefore when you run it, as it's the same exact column it's normal that it apply the same filter on both.
0 -
Based on a suggestion from Jerry, I defined presentation variables representing transaction date range prompts with page level scope for each of three dashboard pages.
When page 1 completes and I select page 2, the date ranges from page 1 are overriding the page 2 date ranges.
Is this an issue where the filters are not defined as protected ? That option does not appear when the filter is defined as 'prompted'.
Thanks again for any suggestions.
0 -
A filter can't use a presentation variable and be "is prompted" in the same time. You need to be coherent in your approach: it's either prompted and it will use the same date for all the analysis, or it uses the presentation variable. You must change your filters.
0 -
To clarify, I am not using a filter\.
I have defined separate presentation variables to handle the date range prompts for each dashboard page.
When I saw that the date ranges for page # 2 were using the date range from page # 1, I was thinking that there might be a way to protect the prompt similar to how you would protect a filter, but I did not see any way that could be done.
Any other ideas are welcomed.
Thank you.
0 -
In the edit prompt dialog, I defined uniquely named presentation variables for each Dashboard page prompt with page level scope representing unique transaction date ranges for each page.
After page # 1 executes, page # 2 shows the same date range as page # 1.
I was able to use the reset option to restore the default values, but am still encountering the unwanted interaction of date parameters impacting other dashboard pages.
0
