Categories
- All Categories
- Oracle Analytics and AI Learning Hub
- 44 Oracle Analytics and AI Sharing Center
- 20 Oracle Analytics and AI Lounge
- 278 Oracle Analytics and AI News
- 56 Oracle Analytics and AI Videos
- 16.2K Oracle Analytics and AI Forums
- 6.4K Oracle Analytics and AI Labs
- Oracle Analytics and AI User Groups
- 103 Oracle Analytics and AI Trainings
- 20 Oracle Analytics and AI Challenge
- Find Partners
- For Partners
Filtering functionality has different results in grammar panel (visual level) and at top level.
Summary:
Content (required):
When a top-level filter is applied, the option to turn off the cascading filter is there from "Auto" to "None".
Top-level filter options:
At the visual level, the option to exclude the cascading effect is not there.
Therefore, the 2 filters may produce different results and these need to be reconciled.
Version (include the version you are using, if applicable):
Code Snippet (add any code snippets that support your topic, if applicable):
Answers
-
Hello,
Limit By operation does not affect the query at runtime but only "limits" the values shown on the other filter categories.
For example, if i had a data setup like this:
Product Category (TV, Games) and
Products - LG, Samsung, Sony (for TV), NFL, Mario, NFS (for Games)
A Limit By operation on Product Category will ensure the respective products are shown as filter values for the user. If i selected TV, Products filter will display LG, Samsung, Sony only.
Acknowledged that the Limit By operator is not available for Viz filters but wanted to make sure that data should not be different on the visualization as long as the same filter values are applied.
1 -
Thank you- yes, I acknowledge that this is a limiting operation.
The visual filter doesn't have the limit by option in the grammar panel and when the filter query doesn't stop running, this would be a useful option to have at the visual level as well.
0
