Best Of
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.
klifford
Color Rules - Conditional Format Font
It would be helpful if were able to set a conditional font format on a KPI card without having to first set a background color. Currently if we want a field to be bold or italic or underlined when a condition is met we have to also declare a background color. We can get away with this by using white or changing the opacity to very low if a different color is used - but today the options are limited. I would like to be able to conditional format font color / font type independently of cell color.
Cross-page filters sharing
It would be really great if page filters could be "shared" across (sub) pages.
Example:
Subpage 1 has filter for Date and Country
Subpage 2 has filter for Date and Category
Users apply Date filter in Subpage 1 (September 5th), then move to Subpage 2 and data is already filtered for the specific date because of the “shared” Date filter
This would allow users to switch to a dashboard from another with a more continuous kind of eploration experience.
As for other features, the feature could be disabled by default in order to preserve the original behaviour.
PantoViz
Configure Instance to Share Beast Modes to Dataset by Default
We would like the ability to set the check box "save as calculation on datatset" to 'checked' by default so that when users are creating a new beast mode it is automatically saved to the dataset. This would save us days of governance and administration work having to clean up multiple beast modes with the same name on a given dataset.
Geoff B
Reusable "drill path"/cards
This request was previously submitted and the support team has instructed me to submit it again:
A common layout for us is to have one dataset with maybe 8-10 cards built on it shared on a single page. We want our users to be able to drill down in those cards and to eventually reach a "base table" that does NOT include all columns of the underlying dataset.
This means that each drill path has to be created and maintained separately for each card currently. It would be better if we could use an existing card as part of a drill path, or at least reuse the drill path view created with one card with the remaining cards so that the work of building and maintaining this doesn't get multiplied by the number of cards.
Column Level Permissions
Hello Product Team,
I have a use case for bringing HR and Payroll reporting into Domo, however, company policy has many permissions/accessibility protocols in place to protect PII data.
We are hoping that at some point Domo comes out with functionality for column level permissions (column level security) as well as integrated/live updating permission groups.
Please consider this for a future roadmap item.
Thank you!
Casey (on behalf of Telus)
