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

Category Filter does not list values when used accross two questions with different datasets #8698

Open
jasongi-actu opened this Issue Oct 16, 2018 · 5 comments

Comments

Projects
None yet
4 participants
@jasongi-actu
Copy link

jasongi-actu commented Oct 16, 2018

  • Your browser and the version: Chrome
  • Your operating system: OSX 10.13.6
  • Your databases: Postgres
  • Metabase version: 0.30.4
  • Metabase hosting environment: Docker
  • Metabase internal database: Postgres

Reproduction steps

  • Create two different datasets (tables/views) with a column called "name", set that to category in the data model and "A List of all values" under "Filtering on this field" in the field settings for both fields
  • Create two questions querying each dataset
  • Create a dashboard with both questions
  • Create a filter and select "Name" from the drop down on both questions
  • Refresh the page
  • The filter will not show a list of all values, it will only show a text box that doesn't search.

I have discovered a work around to this, where if you create a second filter that only filters on one of the questions then it magically makes the first filter (filtering on both) appear with a dropdown again. I've had to name these filters IGNORE ME which isn't a great look for our users.

@poorlymac

This comment has been minimized.

Copy link

poorlymac commented Oct 17, 2018

Hi, another workaround I found is to make the questions SQL questions

@MarkRx

This comment has been minimized.

Copy link
Contributor

MarkRx commented Oct 17, 2018

Looks like #7168

@salsakran

This comment has been minimized.

Copy link
Contributor

salsakran commented Nov 6, 2018

at the moment we take the first card and use that as a canonical set of values.

In general, we assume that a filter will end up pointed at the same column.

@jasongi-actu

This comment has been minimized.

Copy link
Author

jasongi-actu commented Dec 10, 2018

at the moment we take the first card and use that as a canonical set of values.

@salsakran I think this should be classed as a bug rather than a limitation. At the moment when you have filters across different columns then no values appear in the filter list, it does not use the values from the first card.

@MarkRx

This comment has been minimized.

Copy link
Contributor

MarkRx commented Dec 11, 2018

The implementation would not be difficult - for each field pull in N values, combine the results of all, sort them as a set, then only show N values. It could become an issue however should filters becoming more advanced such as being able to filter by a segment (#3015). In that case the filter would become awkward as the segment would only apply to one field.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.