DavidChurchman Coach

With a radial gauge, the implied target is the end of the range (the metaphor of a filed tank of gas). In your picture, that would be 100K. The "Filled" gauge has an option to add a target line that isn't the end of the range: Or the "Comparative Fill Gauge" has a bunch of options for comparing to target, comparing to a…

I think you want to fill down the Profit Center column, and once you've created a filled down Profit Center column, you could filter out the blank Service rows. Here's a good explanation from @MichelleH on filling down using Group-By and Coalesce in MagicETL: I also like the Python implementation from @user01506 (except…

Good troubleshooting. Quick tip: since you're using IN, you could simplify it down to a list instead of a bunch of ORs: WHEN `model` IN ('%F 250%', '%F-250%', '%F250%', '%F-350%', '%F350%') THEN 110 When `Actual bid 2` > 2500 THEN 120 ELSE 110

@trafalger 's solution is really elegant. I was scratching my head trying to incorporate a variable. Probably want a COUNT(DISTINCT product), though, assuming you have more than one customer row per product. Also, note, this will only work with selecting exactly one product. If you want to be able to select more than one,…

You should be able to add your data and series variables as Sorts in analyzer. If you don't specify a sort, it will go in the order of the dataset. If + Sides comes first in the dataset, it will be the first part of the bar or vice versa.

I'm sorry, I misunderstood the question. You want to be able to filter for where the value is NULL in the pivot table. You can't filter for rows in your dataset that don't exist (which is why it's null in your pivot table). I think you want to adjust the data so that there is a row of data for every person for every date…

You could create a beast mode that counts by week (or whatever is defining your columns) and filter by that. Something like: SUM(COUNT(People) fixed(by Week)) Fixed function article:

What would be functionally equivalent is to retroactively calculate what the projections would have been for your entire data set, so you can see historically how your actuals compare to your forecasts. If you're using linear regression, I played with an approach where I tool @marcel_luthi 's data set-up from this thread…

You need to give your "registered" vs. "not registered" column a way to aggregate, otherwise it doesn't know how to collapse the different values. I think this should work (it's basically just wrapping your beastmode in a SUM and another CASE statement) case when sum(case when Year like '%2024%' then 1 else 0 end) > 0 then…

It is not possible to add an x-axis to the Spark Bar (maybe suggest this in the idea exchange?). Alternative: You could add it as part of your data label. You could also use the Flex Table, which allows has the same change indicators, but gives more options for labeling the graph. You could achieve a similar summary number…

Search for the 'Dynamic Columns Brick' in the appstore. It's relatively easy to set-up and does what you're describing in your original post. Otherwise, I would use @michiko's suggestion. Or, if you want a filter that's 'Budget' vs. 'Actual', then after pivoting your data, you could add a column with a case statement like…

I think you want something like: CONCAT( DATEDIFF(QB-Closed-Date, QB-Created-Date), ' ', //days HOUR(TIMEDIFF( QB-Closed-Date, QB-Created-Date)), ':', //hours MINUTE(TIMEDIFF( QB-Closed-Date, QB-Created-Date)) //minutes ) (Adapted from @JaySethi in this discussion)

It looks like you are limiting the data to 150 rows. When you move the Year | Month to your first sort, then it moves the most recent month to the top of the data, and you only get the most recent month. You should remove that limit to see all months. If you're limiting to 150 rows in order to get a more limited number of…

For the mod operation, you can't use %, you'll need the MOD() function. For example, for your hours: FLOOR( (MOD(record_age , 86400000) / 3600000)

The formula should work. I tested it on a similar dataset and was able to get both 'yes' and 'no' values in the control for a by-month bar chart. Two things to try: Maybe try adding that minimum report date as a tooltip to the bar chart? Double check you don't have a card-level filter applied

Yeah, that would be dope. You should suggest this to the idea exchange. I think the greyed out lines in the background would be helpful context. A less elegant way to get that context would be with the shaded upper/lower bounds using the XY line graph. You could plot the minimum and maximum values as the upper and lower…

Your cards seem to agree on an average punch score of 2.84-2.85. Eyeballing your table card, this appears to be correct, because most of your tickets are in the 2-3 range, with less than 500/9K over 4. That narrows the problem to the line graph. I think what Ashleigh was suggesting that If you replace Superintendent with…

You should suggest this in the idea exchange. To me, it sounds like what you're describing is one level of abstraction beyond what GrantSmith is talking about. Being able to reference a BeastMode in another function would be great, but being able to write a custom function that you can then input different columns (or…

100% agree the Domo style is very sparse. Even for dashboards that you're not planning to export to PPT or PDF, it's very difficult to create a page that doesn't require scrolling, where most dashboard guidelines recommend creating something that can fit on a single screen.

You're right. I played around and got CORR(`X`, Y) FIXED(BY Date) (with and average aggregation) to work, with some big caveats: If the standard deviation of either X or Y for a given date is 0, then you'll get a null value. So if you have flat values or vertical values on a given date, or only one value at a given date,…

I was definitely someone that saw the pop-up and then wanted to refer back to it, but couldn't find it. Thank you for posting it here. What's the graph view for Magic ETL? Or is there more information about it somewhere?

Maybe this is outdated, but I linked a discussion of how CORR() doesn't work in BeastMode, but gives the manual formula (credit to @Dean_Wangerin): I was able to test and confirm this BeastMode can roll up correctly by date and by week: (count(X) * sum(X * Y) - sum(X) * sum(Y)) / (sqrt(count(X) * sum(X * X) - sum(X) *…

Unfortunately, you can't hide a column in a pivot table. You could reformat your data before putting it in the table to use the hidden column feature (in a not-pivot table), or you could go even more manual and apply your color rules using HTML: You'll also find many feature requests in the idea exchange for the ability to…

Here's the article with all the different codes for date formats: DATE_FORMAT(`MyDateColumn`,'%m/%d/%Y %h:%i %p') lowercase %h for 1-12 and uppercase %H for 0-23

What's tricky about this is you have three completely different scales you're comparing, and it's difficult to visualize more then two different scales on the same 2-dimensional plane. I might suggest a faceted bar graph instead, which gives a more honest representation of three different scales than laying them on top of…

You could unlock the page and certify all the cards on the page. If someone inadvertently edits a card (instead of save-as), it loses the certification. It also warns the user of this when they try to save the card, which would help prevent inadvertent changes, if not absolutely block them. You could also save a duplicate…

This isn't quite what you're asking for, but on a slicer or checkbox filter, you could set the options to always show the search bar and header. That allows you to type a search term, which dynamically adjusts your filter to just those that contain that search term, and the header allows you to "select all".

I would start by standardizing the date variable. You could use str_to_date: CASE WHEN left(`Date`,1) = 'F' then str_to_date( concat(`Date`,2023), 'F%c%Y') ELSE str_to_date( Date, '%d-%b-%y') END Here's an article on different date transforms: And the different codes for date formats:

Yes!

Whoops, I thought that's what I did