Dear Metabase team,
First of all, thanks so much for this great tool -- I've been working on developing a Metabase dashboard for my company over the past couple weeks and it has been a lot of fun.
I did, however, stumble upon what I believe to be a glitch -- though perhaps it is something I am doing wrong. In any case, I didn't find anything similar in another post or in any current or archived GitHub issue, so I though I'd share it here:
For some context, I am generating this question with the graphical query builder (NOT in SQL), though this glitch seems to occur regardless of how I generate the result.
I am calculating a rate metric ("unlock rate") in Metabase, using the following custom expression:
CountIf(NOT isnull([Redemption Time])) / CountIf(NOT isnull([Created At]))
to basically calculate the proportion of times a voucher is redeemed over the total number of vouchers that were issued -- within a certain group. Basically a slightly more wordy way of doing
COUNT(redemption_time) / COUNT(created_at) in SQL (since there doesn't seem to be a direct translation of the
COUNT() function in Metabase) -- but hey, it does the trick and I'm fine with the result.
The issue, however, is in the rendering: when I run my graphical query, it generates the data in a date format (it should be a floating point number), where every single value is "January 1, 1970, 12:00 AM":
Interestingly, though, when I run the same query (using the SQL generated by Metabase) anywhere else, I actually do see the values, as normal:
Furthermore, I can confirm that this is a rendering issue (and not a calculating problem), because when I turn the query into a visualization, clearly Metabase has the values under the hood somewhere, because the plot looks exactly how I'd expect!
I've tried changing the style of the data on the chart, but nothing that I try seems to work. Somehow the way that the data is being rendered is "stuck" as a constant date, even though the actual values are hidden somewhere but I cannot access them.
When I generate the same data in SQL (even using the exact query that Metabase generates for me after I do it graphically), everything seems to work fine! So of course, I could simply use SQL in the time-being, although my company would like everything as much as possible to be done graphically, which I also understand to be better for the overall user experience with more on-click options, etc.
Could somebody confirm whether this is indeed a glitch with the graphical query builder, and if so, is there something that I can do to fix it?