Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

getDomainAsync returns no values for combined action filter #446

Open
bartoszZamojcinRoche opened this issue Dec 22, 2021 · 4 comments
Open
Labels
Docs Issues with documentation Enhancement Logged Internally Issue which has been logged internally at Tableau

Comments

@bartoszZamojcinRoche
Copy link

Hello,

In the dashboard there is an action filter that is combination of 4 different fields: "Action (Lifecycle Stage,Open Workstep is overdue (group),Product Family (Derived),Role)".
image

The action filter has a lot of values but when I am using getDomainAsync method of CategoricalFilter object it returns no values:
image
image

On the dashboard there are three similar combined action filters and for non of them getDomainAsync method returns any values. There are also action filters that use only one field and for those ones everything works fine.

Bartosz

@bcantoni bcantoni added the Triage New issue which needs to be triaged further label Jan 5, 2022
@johnDance
Copy link
Contributor

johnDance commented Feb 8, 2022

Hi @bartoszzamojcin
The issue here is that values is an array, but in this case, the result is a table, since there are multiple fields involved. Internally, the filter code notices this and doesn't return the table. When the filter doesn't apply to all, the first field values are returned in the filter.appliedValues. For example, suppose I have an action filter on category and segment in SuperStore: "Action (Category,Segment)", and isAllSelected is false. The appliedValues would be as the image shows below.

Is there a way for you to notice this case and work around it? In the future we could enhance getDomainAsync to handle a table of values, but I'm guessing we wouldn't be able to get to it in a timeframe to meet your current needs.

John

image

@johnDance johnDance added Docs Issues with documentation Enhancement and removed Triage New issue which needs to be triaged further labels Feb 8, 2022
@johnDance
Copy link
Contributor

By the way... we need to improve our current documentation on this also.

@bartoszZamojcinRoche
Copy link
Author

Hello @johnDance,

What is time frame for adding the functionality to handle the mentioned case, do you plan to add this any time soon? Also it's important for us from what version functionality will be available as the organization is bit behind the latest versions of Tableau.

Bartosz

@elbandito
Copy link
Contributor

Hi @bartoszZamojcinRoche Thank you for your patience, we're just now starting to look into this from an internal perspective. Unfortunately, I don't have any hard dates on when we expect this to be fixed, but we'll definitely let you know once we have more information to share.

@elbandito elbandito added the Logged Internally Issue which has been logged internally at Tableau label Mar 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Docs Issues with documentation Enhancement Logged Internally Issue which has been logged internally at Tableau
4 participants