Since the 0.33 version I can’t find the link to access to the data model reference (the little book) when I am in simple or custom query builder mode (it still accessible from native query writer)
Did I miss something ? If not could you tell me if it is an error that will soon be corrected or it is a voluntary feature removal ?
Yes, the reference sidebar was removed from the query browser, since it’s mostly a duplicate of the interface - and could lead to misunderstandings, since the sidebar has the real table/column names, which is only needed, when doing a native query.
Are you missing it? If so, can you explain how you used it in previous versions?
You can still access the full reference page if you click “Browse Data” and click top-right link.
That was usefull for our end users, who don’t know our data very well, to check in this sidebar not the name but the description/definition of the different field of the table to know what they can count / filter / aggregate…
Another way to satisfy this use case, even better than the previous one, could be to add field description in “help tool tip” like the ones for main metrics functions :
I understand what you’re asking for. I think the reason is to avoid too many boxes inside boxes (tooltips inside an unknown size select) and to avoid conflict with sub-selects (and the in the sidebar).
@ethach I don’t remember seeing a feature request for tooltip Data Model descriptions, so you can open one if you would like. I still think it’s going to be difficult to fit another icon on the line without making it overly complex. Perhaps it could show the description in a left-tooltip, when hovering the type-icon.
Thanks both. @flamber I’m even thinking just a single button on the page to the existing data reference page would be helpful, since right now a user who wants to understand more about the data they’re looking at needs to navigate all the way there through the data reference button. That requires about 6 clicks and a lot of scrolling in our data, but more importantly requires knowledge of the data structure. So just one button (maybe next to the data title). What do you think?
@ethach Okay, now I understand. I guess it would link to the selected table, and from there the user would have to look at linked tables (if any). I’m not sure what the best user experience would be, but there could probably be several iterations on a design.
Is there any way to create an ERD for an existing DB with Metabase? Or is there anywhere I can find useful information to build one? e.g. fields that have been joined in previous queries and thus are matching IDs…