Categories
- All Categories
- 130 Oracle Analytics News
- 24 Oracle Analytics Videos
- 14.5K Oracle Analytics Forums
- 5.5K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 51 Oracle Analytics Trainings
- 9 Oracle Analytics Data Visualizations Challenge
- 4 Oracle Analytics Career
- 3 Oracle Analytics Industry
- Find Partners
- For Partners
Data Action filter values should pass to one source of filters i.e. Top filter bar workbook filters.
When we use dataaction and pass value to another canvas, all filters should pass to top bar workbook filter.
There is lot of confusion. Filters values distributed to Dashboard filters, Visualizations filters and Top level workbook filters.
There should be consistency and user should understand easily what values are passed.
It will be good if we have passed all values to one type of filters.
It is causing problem in Jan 2024 updates.
If we undo data action , it is clearing top bar workbook filters but not values passed to Dashboard filters.
Comments
-
@Avinash Krishnaram-Oracle or @Benjamin Arnulf-Oracle
Whoever responsible:
I am getting many complaints from teams on how filters works. There is no consistent behavior.
- For data actions, few values passed to Filter bar and few to Dashboard filters and few to Visualization filters.
- If we "Use As Filters" active, Keep Selected & Remove Selected filters applying to selected visualizations only not for entire canvas. With this option I am unable to use advantage of Use as Filters.
As a author of workbook , I can understand but not every user. Always UX should be self explanatory.
Not comparing but FYI...
Qlik passes all filters value to "Filter Bar". Users aware of users applied filters are passed to filter bar not anywhere.
0 -
The target workbook may or may not have the same filter columns. The author of the target workbook may have placed the filter in the top workbook filter bar (pinned vs pinned) or in the dashboard or visualization filter.
The author of the source workbook may not be aware of the target workbook filter definitions. Data Actions will follow the this logic when passing filter context.
- First, if the target have a Dashboard Filter bar where the column participate in, and the filter type match – the Dashboard filter bar column selection will change to reflect the incoming values.
- Second, if no changes are possible to the dashboard filter, the system will look at the top filter bar (workbook/canvas filters). If there is a match to the incoming column selection, the filter bar is visible to the user, and the specific matching filter is visible and interactive (not read/only) – the incoming filter will change the selection of the existing filter
- Third, if the top filter bar or a matching filter is hidden, read-only, the incoming selection will create a new canvas scope filter in the filter bar. Default Limit By behavior will be retained.
2 -
Thanks @Avinash Krishnaram-Oracle
I understood the logic behind it.
But always UX should be simple and self-explanatory. If we share workbook to new user, he should be able to understand what filters are passed and where.
Anyway it is not functional but UX. No issues for me but still you need to consider for better UX.
0 -
@Rajakumar Burra we are planning to change "use as filter" coming next year to make it more author-controlled in respect to the actions following the user selection. The planned change is that the feature will allow you to keep the current behavior or replace it by placing the selected values into a parameter that you can use in specific places across the workbook. Coupled with the ability of data actions to pass parameters as well, you should be able to have an author-controlled consistent method to pass selection within the canvas and to other workbooks.
1 -
This will be of great help to us, thank you @Gabby Rubin-Oracle .
0
