New UX: Filters in Saved View getting overridden by selection made in Context Selector

Options
prakashnishtala
prakashnishtala Member, ALL USERS, Community Member, Certified Model Builder Posts: 4 Occasional Contributor
in User Experience

Observed an interesting anomaly in the New UX.

I have a Time Range for 4 years which I've used as a dimension in Module M. I have displayed this Time Range as a Page Selector and applied a filter to show only 1 year and saved this in a Saved View SV.

Now, when I publish this SV in Classic UX, no matter what year is selected on the published list of Time Range, SV only shows the filtered 1 year.

However, when I publish the same SV to the New UX page, the filter in SV is disregarded. Essentially, when I select any year in the Context Selector, the published SV also changes as per the selected year. However, the filters works fine when the Time Dimension is published in Rows or Columns.

In summary:

Classic UX: Filters take precedence over sync with any dimension

New UX: Filters are overridden when page level sync is enabled

 

Anybody else faced a similar issue? Appreciate any workaround suggestions?

Tagged:

Comments

  • prakashnishtala
    prakashnishtala Member, ALL USERS, Community Member, Certified Model Builder Posts: 4 Occasional Contributor

    Thanks @DmitryP 

     

    Unfortunately, I can't publish these years in Columns. I know, this is going to work very for this use-case where I am filtering for 1 year, but to make it future-proof where the module needs to be dimensioned for 4 years or more, it will be a rework.

     

    Agree, it's a bug in New UX and all the workarounds are going to be manually intensive. 

     

    I am taking the below approach to solve this, which involves no structural change in the model and just 1 touchpoint per page.

     

    I am hiding the non-relevant years from the Context Selector at the top of the page.

Categories