Best Of
Re: Require filter selections
@SlickVic - I agree 1000000%. This was one thing we loved about SQL Server Reporting Services. It allowed us to force end-users to choose required filters before getting data back/seeing visuals. This had a massive impact in saving on the amount of data being crunched and improved the speed of reports/visuals significantly. If Domo had this and you combine it with PDP you could legitimately reduce overhead by an insane margin and ensure very speedy visual rendering times.
Re: Split Column by Number of Characters
Hi Dustin,
You could use the split columns tile in magic etl and use the REGEX option with (?<=.{4}).+ as shown in the screenshots below, just change the 4 to be whatever number of characters you want to split on:
Re: "Add All Columns" button for Mega Table Charts
and a way to click/multi select to add fields instead of having to drag them over.
Ashleigh
Re: Calculate the average normalized score in Beast Mode
You're wanting to do an aggregation of an aggregation (SUM [step1] of MAX [step3]) which isn't possible within a beast mode. You can only do one level of aggregation. You'd need to pre-aggregate your data in an ETL before attempting to do an aggregate within a beast mode.
Re: How to stop a dashboard's background change from impacting charts
"Problematic" is spot on.
I had the same experience with single series charts, they work just fine. But I can't seem to find a workaround for a chart with multiple series. In our world we rarely use single series charts. We're almost always comparing/contrasting products, teams, or other metrics.
In this example, I've got a chart showing production (Y axis) by week (X axis)
No series works fine like you mentioned:
Same chart with a series, default view:
My main issue is if you highlight one of the series, the rest can't be read. The only exception is highlighting an individual week:
It'd be really nice to be able to see all the values at a glance. They can't really glean much insights if they have to highlight every single block one at a time.
The fix seems to be:
- Prevent font changes on a page from impacting cards
- Allow users to change the default color for unselected parts of the chart. (From grey to black for example)
Bummer there isn't a fix, but you did just gain a new YouTube subscriber at least! As always Mark your insights and help are greatly appreciated.
Re: How to stop a dashboard's background change from impacting charts
I'm not surprised if you are having trouble as I have found changing background colors to be problematic. I believe there is hope in the coming months with the release of App Studio that was shown at DP23.
However, I tested changing my dashboard background to black and the card background to black and left the hover text settings at their default configuration and it adjusted properly for me.
I would try resetting your chart properties and see if it handles the black background properly.
Hope this helps.








