How to Populate Metabase Dropdown Filter with Conditional Data from MongoDB? (Filter by Status = "active")

Get Help
1

We are using Metabase connected to a MongoDB data source. We want to populate a dropdown filter using values from a collection named A, but with a condition based on a dynamic status variable, not a hardcoded value.

Suppose our MongoDB collection A looks like this:
[
{ "_id": "1", "name": "Record 1", "status": "active" },
{ "_id": "2", "name": "Record 2", "status": "inactive" },
{ "_id": "3", "name": "Record 3", "status": "active" },
{ "_id": "4", "name": "Record 4", "status": "pending" }
]

We have a dropdown filter for name field values, but the records shown in the dropdown should depend on the status.

For example:

  • If status = "active", dropdown shows: Record 1, Record 3
  • If status = "pending", dropdown shows: Record 4
  • If status = "inactive", dropdown shows: Record 2

In short, the list of dropdown options should be filtered based on the value of a status variable, which could itself come from another filter or be passed to the question/dashboard.

2

Hello there,

I believe you're looking for linked filters on dashboards. So you would have a status filter and a name filter that has the other filter as its parent. Would that work?

3

Thanks.
Yes we need similar functionality, but in our case we need to pass status filter from API.
We need to display Record name in dropdown and use _id as value.

4

Hmm do you have a more concrete example to illustrate what the use case would look like?
You could use URL params to pass filters. Do you want the filter to show "Record 1" and when it's selected, filter by _id = 1? You can customize filter display values (with the Edit button at the right of "Dropdown list") but this can't currently be combined with linked filters

5

you can't pass in a resultset from an API natively, it's not supported from what I can see, unless you have your own embedded dashbaords I guess?
Other option is to populate a table with those values periodically and then map filters to that particular table/field in your db.

There could be a funky way to perhaps do it using the metabase api also I guess but I think you'd need to store the values in a db ultimately.

6

We are building a Dashboard in Metabase using our Opportunity collection. We want to implement two dependent filters:

:one: Company Filter

  • Type: Dropdown
  • Filters by companyId field in Opportunity collection

:two: Pipeline Filter (Dependent on Company)

  • Should display pipeline.name in dropdown
  • Should send pipeline._id as filter value in query

Example Schema:

Pipeline Collection:

{
  _id: ObjectId,
  name: String,
  companyId: ObjectId
}

Opprtunity Collection:

{
  _id: ObjectId,
  name: String,
  email: String,
  mobile: String,
  companyId: ObjectId,
  pipelineId: ObjectId
}

What We Need:

:white_check_mark: Pipeline Dropdown should:

  • Only show pipelines for the selected company
  • Show pipeline.name as dropdown label
  • Use pipeline._id as the filter value in the query

Current Challenge:

  • We are not sure how to configure the Pipeline filter in Metabase so that:
    • It depends on the selected company
    • It shows name but sends _id in queries
7

Hi, I used to denomarlize the model and use the name in the final dataset as a filter, in your case, add the pipeline name on the Opportunity collection, and use it in your filter.

8

Question:
I have four tables: state, district, block, and village. I’ve created four dropdown filters in Metabase based on these tables.

Now, I want the dropdowns to be dependent — for example, when I select a state like West Bengal, the district dropdown should only show districts related to that selected state.

Is this possible in Metabase (free version)?
Please give me a clear "Yes" or "No"; if Yes, explain how to implement it.

9

Hello sourav2,

Yes, it can be done with linked filters. Instructions are here:

Please post a new topic if you need to discuss your specific situation.

10

We can't use name as it may not be unique, any other options?

11

No problem, METABASE will do the "distinct"

12

If the name::_id mapping isn't unique, you need to build a model or view that provides a 1:1 mapping between a display name and _id (append the _id to the name or something). Join that model or view to your query to map the filter name.

EDIT: Another option -- Metabase may actually know how to do this internally. Set the _id field as an Entity Key an the name field as an Entity Name in the table metadata and use a field filter -- Metabase may do the mapping for you. It was discussed in this thread: