Best Of
Re: Schedule App Studio Reports
Upping this! Our team is really looking forward to seeing this feature live.
Re: Reusable "drill path"/cards
I would love to be able to Save a Drill path to a Dataset (and give it a decent, descriptive name) so that when I go to create a drill path for a report, I could choose from an existing drill path.
Stacked Waterfall Graph
Please could a stacked waterfall chart be added as a standard card type within Domo?
Here's an example from the web.
Thanks!
Customisable Line Type and Symbol in Line Chart
Would like to be able to assign a line type (including dashed) and symbol based on Series value - in the same way that we can set colour rules.
Add tooltips to all chart types
Can we have tooltips available in all chart types? For example using a funnel chart tooltips section is greyed out.
Editing All Cards in a Drill Path
Currently in Domo, if I make a change to the top card in a drill path, that change doesen't apply to other cards in the Drill Path. It'd be very useful if there was an option to apply any changes to all cards in a drill path at the same time, rather than editing each individual card.
Pill formatting for Variable
Hello, I use Pills for Filters frequently. I'd like to use Pills for Variable controls as well.When using Pills for filters, I create a card and enjoy the format options in Analyzer, such as to center and fill Pills with the content. How can I achieve this using Variable controls? I have not found an Analyzer for variable control. Thank you.
Save and Run vs Save As
Bad idea to change the Save options in the ETL. I've been shooting down to the bottom option "Save and Run" for years. I've already duplicated multiple datasets working fast, have to back track, delete the duplicates, and update the actual ETL.
a10hall
Re: Dashboard Layouts - Control Padding Between Cards
@MarkSnodgrass This is currently on our roadmap and we are scoping ways that could allow users to adjust spacing on dashboards.
Khushboo
Filtering on missing / null values is awful - improve it!
TLDR:
If a column contains a null value, there is no way built into the UI to filter to select null values only. Additionally, if you happen to choose "NOT IN" as your filter type and select a value, NULL values will additionally be excluded even if not requested.
I understand that there is a workaround using beastmodes, but this shouldn't be required. Additionally, the "NOT IN" scenario that excludes NULLS is actively giving people incorrect results.
/TLDR
DOMO has approached the topic of how to filter missing values with a developer centric mindset instead of a business user mindset, and this needs to change. The users expected behaviour when they go to apply a filter and select an "empty" box to see all the missing values… is to see the missing values. Likewise, if the consumer selects 'NOT IN' and chooses a single value, they don't expect anything they didn't select to also be filtered out.I understand that when doing comparisons to NULL values in the database layer this is the 'correct' answer, but that isn't helping your customers get the answers they need. It's just causing frustration, errors, and wasting people's time. Not only this but it erodes people's confidence in your reporting platform - our accounting team doesn't understand why filtering on a value using "IN" and then filtering on the same value using "NOT IN" doesn't line up to the unfiltered total, and I don't blame them.This is probably my most frequently run into frustration with DOMO, and I know that it bugs many other users that I speak with as well.
To my knowledge, the only current workaround is to write a beastmode to make the desired comparison and then use that as a filter - but that's a horrible experience for the average non-technical user, and a very poor experience for the average technical user.
I can only imagine how many people are currently making decisions based on incomplete results due to this mishandling of the current filters.
Please, please, fix this.