Oracle Analytics and AI

Allow default filter value in DV to be set by RPD variable

Organization Name

University of Texas at Arlington

Description

Allow DV to use RPD variables as a default filter selection. In DV, when creating a List View item to use as a filter, there is a Default Value option. You can set this, but it only uses the text entered and will not convert variable calls to the variable value. For example, if you enter VALUEOF(USER_DEPT) then the filtered selection will be "VALUEOF(USER_DEPT)" and not the assigned variable from the RPD.

Use Case and Business Need

In Analytics, you can use an RPD variable to set a default value for a dashboard prompt. In our case, this allows financial dashboards to default to a users department but still allows them to select other values.

More details

I know you can you use an Expression Filter in DV to call RPD variables, but this restricts the entire filter. All we are looking to be able to do is to set a default value but not limit the other values in the list box.

Original Idea Number: 8bea4d897f

Find more posts tagged with

Delivered

Reporting

Data Connectivity

Analysis and Data Visualization

Administration

Status: Delivered

Comments

Greg Faris

This is definitely needed and required to make the filters as dynamic as needed. We do this with every one of our Answers dashboards to set our default timeframes using specific date ranges that are based on repository variables. The flexibility is not there in the current DV filters. This would be good to see implemented with the presentation variable request (https://cloudcustomerconnect.oracle.com/posts/db4b7a2965). We would like to see this combined with the ability to leverage the TIMESTAMPADD function on date variables similar to Answers prompts.

We have been trying to workaround this for a while, but it would be good to see priority put on this request. It has really hampered us to develop the views we've needed since we began using DV.

Screenshot 2021-06-15 101618.jpg

Michal Zima

I think this would be doable with parameter binding - you will define parameter, whose initial value would be logical SQL, referencing RPD variable and then you can bind that parameter to filter column.

Gabby Rubin-Oracle

@Michal Zima is correct; this can already be done with Parameters.