Need to display all data in filter widgets using category field filter

Probaner · April 11, 2018, 9:18am

I have around 900 distinct data in a column, whose type I have set to category. Used the same from native a SQL editor as a field filter. Everything works fine. I just need to display all data in filter widgets instead of text box. What I understand there is a condition of count less than 300 …In the code base. I want to modify it and make it 1000 and do my own build. Please provide some hint which file to edit and how to proceed with build what stack needed to be in my local m/c , অন windows

AndrewMBaines · April 11, 2018, 10:28am

First advice would be to give up trying to develop using Windows. I’m 100% Windows here, but still used Ubuntu in a VM for Metabase work. If you’re running Windows 8 or later, you have HyperV.
This was the first time I used Ubuntu, but it wasn’t that bad.

After that, I can only point you to:

github.com

metabase/metabase/blob/master/docs/developers-guide.md#build-metabase

**This guide will teach you:**

*  [How to compile your own copy of Metabase](#build-metabase)
*  [How to set up a development environment](#development-environment)
*  [How to run the Metabase Server](#development-server-quick-start)
*  [How to contribute back to the Metabase project](#contributing)
*  [How to add support in Metabase for other languages](#internationalization)


# Contributing

In general, we like to have an open issue for every pull request as a place to discuss the nature of any bug or proposed improvement. Each pull request should address a single issue, and contain both the fix as well as a description of how the pull request and tests that validate that the PR fixes the issue in question.

For significant feature additions, it is expected that discussion will have taken place in the attached issue. Any feature that requires a major decision to be reached will need to have an explicit design document written. The goals of this document are to make explicit the assumptions, constraints and tradeoffs any given feature implementation will contain. The point is not to generate documentation but to allow discussion to reference a specific proposed design and to allow others to consider the implications of a given design.

We don't like getting sued, so before merging any pull request, we'll need each person contributing code to sign a Contributor License Agreement [here](https://docs.google.com/a/metabase.com/forms/d/1oV38o7b9ONFSwuzwmERRMi9SYrhYeOrkbmNaq9pOJ_E/viewform)

# Development on Windows

The development scripts are designed for Linux/Mac environment, so we recommend using the latest Windows 10 version with [WSL (Windows Subsystem for Linux)](https://msdn.microsoft.com/en-us/commandline/wsl/about) and [Ubuntu on Windows](https://www.microsoft.com/store/p/ubuntu/9nblggh4msv6). The Ubuntu Bash shell works well for both backend and frontend development.

This file has been truncated. show original

maz · April 11, 2018, 4:40pm

No need to modify anything — we're releasing a big update to how this works in Metabase 0.29, where instead of a text box you'll now get a search box with autocomplete if there are more than 100 distinct values.

filters

Probaner · April 12, 2018, 5:48am

Any hint when this release is scheduled? Would plan accordingly.
Thanks for replying.
Also I need to bring up cascading filters (as drop-down) on my dashboard/questions. Any way to achieve that or it is also planned in upcoming release?