I have created a dashboard which I expect to be able to choose from a series of filters which can either be a dropdown or search box.
However, this is not the case, as the filter does not show autocomplete options in the case of a searchbox, or a list as relates to dropdown.
Not sure why this happens, however, I suspect that I'm not doing something right.
Disclaimer - The dashboard feeds off widgets which use saved questions as the source of the data. This saved question in itself is derived from native SQL.
It's not possible for Metabase to show dropdowns from SQL results.
https://github.com/metabase/metabase/issues/5594 - upvote by clicking on the first post
You'll either need to use Models https://www.metabase.com/docs/latest/data-modeling/models where you map the field in the model metadata, or create a View directly on your database.
Yes, you're right @flamber, It works now.
However, there's an instance where I have 2 columns which reference the same table column.
When that happens, it makes the filter values the same for both columns.
Any workaround for this, or is this even a known issue?
Not quite what I need.
As shown below, there are 2 columns which reference the bank table, FUNBANK and BENBANK
The FUNBANK was mapped first, before BENBANK.
When filtering the report, there are 2 instances of FUNBANK showing .
@oaajibade I don't understand your problem then. Create a View on your database, so Metabase just has a single column to deal with.
When a model has 2 or more columns which map to a specific table column, e.g. Funding Bank & Beneficiary Bank are 2 columns which map to the bank table.
Because the columns in the model both map to the same table, it replicates their result.
E.g. If I choose Bank A as the filter value of Funding Bank, It would also show Bank A in the Beneficiary Bank filter.
The column names also changes to the column which was first mapped.
I hope this helps understand the problem I'm facing
@oaajibade Create a View on your database instead. There's several issues with Models, which won't be fixed until v45: https://github.com/metabase/metabase/issues?q=is%3Aissue+label%3AQuerying%2FModels+