You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hope it's okay to drop in with another feature request. As I roll out Metabase, these are coming to me organically from time to time.
Something that strikes me is that as the system begins to scale, it quickly becomes hard to retrieve visualisations through the "quick" mechanisms of searching in the search bar and choosing from one of the dropdown populations.
Something I think that would be very valuable: every "entity" that you create (whether that's a dashboard, a question, a model) has an entity ID (I imagine this already exists in the backend).
Here are a couple of ideas for how this could be useful:
1: Permalink masking: visit yourmetabase.com/[entityid] to jump to the target URL
2: To expedite retrieval of the right visuals between colleagues. For example, I could tell a colleague to search for 12345. If this retrieved the desired entity there would be no chance of ambiguity if objects with similar names were stored in the system.
Daniel
The text was updated successfully, but these errors were encountered:
Hi guys,
Hope it's okay to drop in with another feature request. As I roll out Metabase, these are coming to me organically from time to time.
Something that strikes me is that as the system begins to scale, it quickly becomes hard to retrieve visualisations through the "quick" mechanisms of searching in the search bar and choosing from one of the dropdown populations.
Something I think that would be very valuable: every "entity" that you create (whether that's a dashboard, a question, a model) has an entity ID (I imagine this already exists in the backend).
Here are a couple of ideas for how this could be useful:
1: Permalink masking: visit yourmetabase.com/[entityid] to jump to the target URL
2: To expedite retrieval of the right visuals between colleagues. For example, I could tell a colleague to search for 12345. If this retrieved the desired entity there would be no chance of ambiguity if objects with similar names were stored in the system.
The text was updated successfully, but these errors were encountered: