Categories
- All Categories
- 5 Oracle Analytics Sharing Center
- 11 Oracle Analytics Lounge
- 194 Oracle Analytics News
- 41 Oracle Analytics Videos
- 15.5K Oracle Analytics Forums
- 6K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 68 Oracle Analytics Trainings
- 14 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
Provide Prompts within the DV Dataset reload dialog and corresponding variables in dataset queries
We would like to see in the DV dataset reload dialog something equivalent to what we have in the Classic dashboards or publisher reports we were previously using in OBIEE i.e. equivalent to Dashboard Prompts or Publisher Variables. We have shifted to using DV datasets because it is a great solution for extracting data from complex databases doing it in multiple steps and joining in the dataset. So our OAS analysis queries are used in datasets and not anymore in dashboards. But we lose the flexibility to have users select their time period, their product, etc.. Could this be added inside the dataset reload dialog (both manual reload and scheduled) with corresponding variables (prompts) used inside the analysis queries. This would then be close to the perfect solution for our business needs in the area of drug safety reporting.
Note that we cannot use the concept of presentation variables in the dataset because the size of our database makes it mandatory to apply variables/prompts inside the query which extracts the data from the database.
Thanks for looking into this request!
Comments
-
As a work around currently -- a user could edit the dataset definition with a filter and then reload.
If it were via some kind of variable, would you set it for every dataset reload or you would you want it to be driven by something like an RPD variable which changes independently.
0 -
Hi Bret :
As a workaround we currently have analysis filters (in our Classic UI) which the business user updates. It is not very practical for them in terms of finding the filters. Also when duplicating workbooks we have additional work to adjust them.
We would like variables like our BI Publisher or Dashboard prompts which appear in the dialog with drop down lists and the user can select them for every dataset reload : ideally previously selected values should be shown/used by default. The drop down lists as we have in Publisher and Dashboards are important so that only valid data can be selected. We use RPD session variables a lot but in this context they might not be very useful for us.
This combined with a good duplication of Workbook/dataset would allow us to have our gold workbook/dataset and quickly create several workbooks (by duplication) with a different select of time periods and product.
Thanks for your feedback, Philippe
0 -
Have you tried using Edit Definition after it is copied?
0 -
We use Edit Definition when we duplicate a gold workbook to a 'child' workbook which will apply to a particular product. It is a lot of work to update the definitions to the corresponding product specific analysis queries since we have datasets with multiple queries. We would like to make this transparent by having the analysis queries (filters) use variables (same as dashboard prompts) and refers to these prompts in the dataset reload dialog.
This is something business users would absolutely love because they cannot handle changes e.g. in edit definition.
0 -
I would like to clarify that this enhancement request boils down to have in the dataset reload dialog the dashboard prompts functionality (we currently have in dasbhoards) including the possibility for the dashboard prompt to generate presentation variable values which can be used in the analysis advanced tab set variables for use in session variables. The OBIEE dashboard prompts functionality should be implemented inside the dataset reload allowing to make the dataset analysis queries dynamic and we should then have the solution business users need.
0 -
Can this idea be submitted to voting and get an idea number?
For our Lifesciences reporting solutions this idea / enhancement request is critical.
0 -
This idea is critical for our safety projects where the dataset generation has to be flexible e.g. setting time period start and end dates and selecting products or studies which will be taking into account by the queries which load data in the dataset. Our queries are currently using always analysis with RPD. The functionality we need is similar to the classic dashboard prompts with their presentation variables used in the queries including in the prefix for setting session variables.
We have implemented successfully a workaround which comes at a cost in terms of implementation : we have build a custom table (OAS report parameters) which contains the report names and their parameters and we have created an analysis/dashboard WRITE BACK page to allow users to update the parameters for their reports in this custom table. Then in the RPD and in the queries we have added logic which in case a report exists in this table, the logical SQL picks up the parameters automatically. Thus the dataset generation is now dynamic and when duplicating datasets (e.g. from a template to a specific set) we have also not a lot of work to do except adding the new report in the table. Before our workaround making changes is long and error prone.
We can demo this solution anytime when required to OAS team to illustrate what we need. We would love being able to remove our workaround and have the dataset generation dialog allow to cover all of this by taking over the dashboard prompt functionality including its features with presentation variables inside the dataset generation dialog and being able to refer to these prompts/presentation variables in the dataset queries.
Thanks for looking into this. Note that our requirement is on dataset level not workbook level as we must be able to restrain the volume of data going into a dataset to specific parameters otherwise we end up importing our entire database into our dataset.
0 -
I believe this is similar to using parameters in a dataset or query within the Data Model Editor in Analytics Publisher. Sometimes, loading the entire dataset isn't feasible due to size or performance constraints.
Instead, allowing users to load and visualise just a portion of the data, such as a specific date range, allows for more focused insights and better performance. This approach also provides flexibility, as users can dynamically adjust filters (like changing a date range) just as they would modify parameters in an Analytics Publisher report.
0
