-
Add Distinct/Unique COUNT to Analyzer Dropdown Aggregations
Creating beastmodes just to count a distinct value adds additional clutter that could be minimized by adding distinct counts to the list of aggregations on a card.
-
Add Beastmode Link to Formatting Dropdown for Columns Used in a Viz
Seems odds that it is so difficult to find and open beastmodes that are actively used in a card. Would love it if there was a link added to the dropdown menu where the column formatting options are. There are many times users need to go troubleshoot a BM but we have to go search through all BMs just to get to the ones that…
-
Dataset Naming Walkthrough Wizard
Even with a dataset naming schema in place, it is very easy for datasets to get messy with a multitude of users creating deliverables. It would be great if there was a customizable dataset naming walk-through wizard that can be required for all net new datasets (ETL, VIEW, etc), that auto-generates the dataset naming…
-
Fiscal Calendar in ETLs (for Aggreagations)
To my knowledge, the only place that you can use a fiscal calendar is at the card level. There are times when aggregations in an ETL, are just unavoidable. It would be great to be able to do these aggregations using the imported fiscal.
-
Indicator on dashboards to visually show user that a card is new/has been updated
Often times users miss updates on pre-existing dashboards or they do not realize a new card was added entirely. I would love a way to configure a "pop-up" message that a user must click out of the next time they log in (similar to how DOMO pushes new features available). Within the message I would like to be able to give…
-
Add a Link to Input Dataset Details in MAGIC UI (Similar to Lineage "VIEW" Button)
There are many times when users are in an ETL troubleshooting, and need to open one of the input ETLs for further investigation. Currently there is no available link in MAGIC that will take you to your input dataset's details. Something similar to lineage to "VIEW" the dataset, would be very useful and save quite a few…
-
Lock Fields in "Data" view on a Dataset
As datasets mature overtime, new fields get added that cause users to need to scroll through the schema in order to find critical fields (primaryKeys). Would be great to be able to "lock" whichever fields you'd like, so that they always stay left adjusted in the Data view.
