Best Of
Ability to override Colour Source colours on Filled Gauge cards
For this particular example, I'm using a filled gauge which has the ability to automatically change the colour based on the target value by selecting either "Green Above Target" or "Green Below Target" resulting in the below red or green.
The problem with this is that the specific green and red that the card uses is locked which;
- can conflict with other shades being used on a dashboard
- reduces ability to utilise accessible colours for people with colour blindness
This card type (and any other that has similar functionality) should have the same ability as the comparative gauge chart which enables you to select the positive and negative colour by the colour picker/hex code.
Craig_Lynch
Surface more details on connector indexing errors to help us to be able to see the cause.
The error we see in Domo:
Domo has received your data, but there was an error in processing. This will automatically be corrected the next time this DataSet runs.
Error details extracted from Support:
"Indexing failed: Empty primary key at row "0" column "Ordernumber",
If more of the message was shown in the front end of Domo the customer would have been able to isolate the problem quicker.
Show Column Description on Column Hover in Table Cards
As a way of shortcutting a data dictionary card - it would be very useful if you could hover over a column title and have the column description show as hover text. Or even have the ability to add custom hover text to each column via the card editor here.
lhrogersiv
Mass Deploy Drill Paths
I generally want a structured layer between visualizations and the default drill down data.
If I have 30 cards on a page I would have to build this 30 times.
Allow developers to assign or copy/paste a card structure into any drill path.
jroach
Dashboard Editing for Different outputs
Currently under the 'Edit Dashboard' option, there are 2 options to choose from: Desktop and Mobile. These are really powerful for customising the layout and sizing between the two device types, however the mobile is really specific for phone, and when viewing dashboard on an iPad/tablet the customisation doesn't render the same.
It would be great to see a Tablet option which would enable the dashboard to be customised to suite the device better.
The same approach could be applied to a PDF/PowerPoint option, enabling the dashboard layout to be customised against each of the pages. Rather than relying on the automated layout, cards that should be grouped on the same page could be, and avoid cases where they're split across different pages. Currently you need to insert borders, and use trial and error with the sizing of the cards to try and get it as close as you can which requires compromising either the dashboard layout or the PDF/PowerPoint layout.
Allow Group Ownership of Magic ETLs in DOMO
Currently only Datasets can have group ownership, however it would be a great timesaver if a group can have ownership of an ETL in Domo. It would make ownership more streamlined and controlled.
tanayakakade
Re: Count number of character occurrence in string
You can calculate the length of the string, remove the character you want, recalculate the length and take the difference.
LENGTH(`Color`) - LENGTH(REPLACE(`Color`, ',', '')) + 1
Change Data Capture (CDC) on Domo Datasets
It would be useful to have CDC capability on Domo datasets, creating a journal file of all changes to a dataset such as deletions, insertions, updates so that they can be tracks and potentially acted upon.
mdekonin
Enable Card Descriptions to show up on scheduled reports
We need card descriptions to show up on scheduled reports. I know other users have also suggested more customizations to scheduled reports to better control how the emails appear and I would be for that as well. Thanks!
MattGo
Options for Preview Run Limits in Magic ETL
The Magic ETL currently only max out at 400k row for the preview run from your input datasets. This is limiting the test preview in your flow as it only picks (from my understanding) the first 400k row of your dataset. So if you're trying to preview your actions (such as filtering) you may not get anything showing in the preview if the value which you are filtering only exists from row 400,001 onwards.
Suggestions for Domo team could be:
- Remove limit
- Allow user to select row limits by datasets
- Allow users to select dataset row ranges if the limit has to remain, for example, if Domo needs to stay with the 400k limit, then allow users to select which rows range for the limit to be applied, i.e. row 200,000 to 600,000
- Keep existing limit but allowing additional limit parameters such as date range, i.e. set 400k limit for MMM to MMM of YYYY