Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture
Comments
-
Jerry Thanks for offering that solution. I will proceed based on your instructions. Jim
-
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…
-
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…
-
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…
-
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…
-
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…
-
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…
-
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,…
-
Gianni Your post regarding the logs has been helpful. For five dashboard pages, I have defined all the date parameter prompts with "page level" scope. When dashboard page # 5 is launched, the analysis on that page is invoking predecessor analyses on other dashboard pages, The problem is that an analysis on page # 1 is…
-
To clarify, each report is an analysis object created from OBIEE answers that I am attempting to migrate to the dashboard framework to avoid hard coding of date parameters. As suggested, I will ask the DBA for both physical and logical SQL logs to assist in isolating the issue. Thanks for your responses.
-
Gianni & Christian Thanks for your input. I am not using BI Publisher. I am converting reports, each of which were created as an analysis, to run from the dashboard with prompts for date ranges so that the dates are not hard coded within the analysis filters. I am at a loss to explain why the dashboard functionality is…
-
Gianni Thanks for your input...in this case, the analysis based reports and the Dashboard based reports are in separate catalogs. Also, I created the analysis based reports earlier in the project and am trying to replicate the same functionality from the Dashboard. My plan is to ask the Administrator to provide the query…
-
Updating the value for the parameter MAX_EXPANDED_SUBQUERY_PREDICATES to 25K from 8K resolved this issue. Thanks to Gianni for offering his input.
-
This is not BI publisher, but analysis that I placed in the Dashboard. Overnight tonight,(6-12), the DBA is going to bump the MAX_EXPANDED_SUBQUERY_PREDICATES TO 25K from the present 8K & recycle the DB instance. I assume that the database is triggering the exception & not OBI, but I am offering the error text below....…