Filter values in Tableau and appliedValues of CategoricalFilter from API are out of sync in context of "connected" filters

[bartoszZamojcinRoche]

Hello,

Below description of the issue using one of our dashboards as an example. On the dashboard there are 3 filters: Community, Affiliate and Country (lets focus only on Affiliate and Country). When i.e. in Affiliate filter I select four values that also limits available values in Country filter everything works fine:

But now when I unselect something in Country filter, i.e. Argentina and Austria, this is reflected in Tableau front-end Affiliate filter but from Extensions API backend, in Affiliate filter object I still get four applied values:

It seems that the issue appears when one filter limits the second one and then the second one limits the first one, which looks like a problem with sync between Tableau frontend and Extensions API backend. If I am unselecting values in only one filter then everything is ok. I have checked this behavior on two dashboards with the same result.

Bartosz

[johnDance]

I have duplicated what you have reported, and am having our filters team investigate what is happening. John

[johnDance]

Hi Bartosz: I know this is ironic given what I said for issue #446 , but you want to use getDomainAsync here. That will give you the proper items in all dependent filters. For example, in your example above, after selecting 2 countries, if I use getDomainAsync on the affiliate filter, I get:

Let me know if you have any questions. John

[johnDance]

I'll get the documentation clarified for this.

[bartoszZamojcinRoche]

Hi @johnDance ,

I've checked proposed solution and it works only partially. When I am using getDomainAsync with 'relevant' as argument I got correct values that are also selected in Tableau filter, so Albania and Algeria using the above example. But when I unselect one of this options in Tableau then from the domain I am still getting two values and in the availableValues of filter object there are still incorrect, additional options that are not present in Tableau filter so I can't use either.

Additionally shouldn't this behavior be qualified as bug? Extensions API provides different values than there are in reality, in Tableau frontend.

Regards, Bartosz

[johnDance]

Hi @bartoszZamojcinRoche Thank you for investigating it more. I'll get a defect written up for the filters team. John