nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Oracle Communities

Oracle Analytics and AI

Child Item

Keep Selected / Remove selected behavior should be consistent across all workflows.

Rajakumar Burra

Current behavior is very much confusing.

When we use Keep Selected/Remove selected in any DV, respective filters are applied to Canvas filters . Users understand it very well what added and what removed.

But if the DV is enabled with "Use as Filter" and when we use Keep Selected/Remove selected in any DV, respective filters are not applied to Canvas filters. It is just removing or adding to selected filters and even it is not showing anywhere what filter is applied. It is full of confuse what user is doing.

Also if the DV is enabled with "Use as Filter" , custom Knowledge fiscal calendar values are not working .

@Avinash Krishnaram-Oracle Overall "Use as filter" is not consistent. Also I have raised a Bug 37806446 . It would be good if you consider for fixing confusing behavior and incosistent UX.

Find more posts tagged with

Under Review

Status: Under Review

Comments

Avinash Krishnaram-Oracle

Discussed with Raja and based on his feedback: the product adds a viz scope filter when performing a Keep Selected operation on a viz that is enabled for Use as Filter. Reproduction steps:

Add a 2 viz on the canvas - Viz1, Viz2
Enable Viz1 as Use as Filter
Select a mark on Viz1 - this will pass the context to Viz2 and add a viz scope filter on Viz2
Select the same mark on Viz1 and perform Keep Selected - this adds a viz scope filter on Viz1 instead of creating a canvas scope filter on the top filter bar. This inconsistency is causing confusion for PTC end users. Apparently in some scenarios, the Keep Selected action on step 4 does not create a viz scope filter.

Avinash will follow up.