DavidChurchman Coach

Is he going to show us some of his MagicETLs? I'd be curious to see if he color-codes his strings between tiles, or how much he uses the notes.

+1 to more customizability of Pivot Tables. They've gotten a lot better in the last year or so, but still have a lot of unrealized potential.

Agree, this would still be helpful

The way I would approach the "master" filter is using a variable, and a BeastMode filtering against that variable on each card. case when month(Date) = Variable then 'Include' else 'Exclude' end (Filter for "Include") Then, when you need to change the whole dashboard, you can use a Control to change the variable for the…

One approach is to have a "raw" dataset with no BeastModes, and then save a view of the dataset for each distinct use/dasbhoard. Each view can have its own BeastModes. You can also limit the number of columns and rename the columns going into the dashboard, which can make the filters on the dashboard more user-friendly.

Yes! This would be great!

These are a collection of links to other ideas suggesting the same thing (descriptions in the email and/or PDF/PPT exports). Maybe we could upvote all of them? Or consolidate all their votes onto this idea?…

As an addition, descriptions also don't show up on PDF/PPT exports, so that's also not an option. Descriptions should 100% be included in every output and it's maddening that they're not.

Here's a recent discussion of someone working through the same issue: https://community-forums.domo.com/main/discussion/69044/need-help-changing-to-last-12-months-and-sorting-in-proper-order#latest

For the first part of your question, you just need to use a sum as your aggregation, and then you can put a quick-filter on your date: The second part is slightly harder, as you need the total to stay the same regardless of filter. You can use a FILTER NONE in a FIXED function to do that:

Yes

This is less visual than what DashboardDude made, but I feel like it should be said there is "official" documentation here: https://domo-support.domo.com/s/topic/0TO5w000000ZaoeGAC/chart-types?language=en_US

Since you're using the pivot table, it needs some way to aggregate the value. Since it's a text column, the only default is a count. Pivot Tables can be a little particular, and sometimes will fight you on having text display. The most reliable ones I've found are something like: CASE WHEN COUNT(`Nu`) > 10 then 'No' else…

It's basically 2 steps. 1: split your Dependent column using the delimiter. 2: unpivot your data long. I also use the "Alter columns" tile to drop unnecessary columns:

I think you could create a BeastMode for your sort: MOD( MONTH(`addTimeStamp`)+12 - month(current_date()), 12 ) Add 12 to your month and subtract the current month. Then use modulo 12. If the current month is March: March + 12 - March = 12, Modulo 12 = 0 April + 12 - March = 13, Modulo 12 = 1 … January + 12 - March = 10,…

Can you create a fake version of your two datasets with at least a few rows of what the data looks like? That will get you a fast, more reliable answer. Based on you've said so far, I think what you'll need to do is pivot your Salesperson data long and join on the operation and product with the other table. To do the…

GrantSmith's restructure would be more dynamic than what I'll suggest, but if you want something a bit simpler: Approach 1: ETL a Baseline Column All of your 7 BeastModes are comparing to the same baseline. You could just use an ETL to filter for that baseline data and join it back as a "baseline" column to your dataset,…

The "DISTINCT" in your COUNT(DISTINCT) will make it so each student is only counted once across whatever level of aggregation you are using in your card. Since students tend to be the same across fall/spring/summer, your count across the terms will be closer to the count of a single term than the sum of the terms. That…

The dataflow is working again, with no changes from me. It was probably some update? Maybe I should add "wait a couple hours" to my troubleshooting toolkit.

I can't tell from you've written if your problem is A) the graph goes to 12/2025, even though you only have data through 1/2025. B) It's hard to see the "action", because the y-axis goes from 0 to 40M, even though the values are all in the 25M to 35M range. If it's A, then you need to filter. You could filter for Actual RM…

What happens if you try making the cards larger? I think sometimes different browsers resize/reformat a little weird

Because I'm so bad with FIXED formulas, I would personally probably approach this at the ETL step. If you do your FBA/WFS in the ETL before filtering the "On list", it should work.

Is Financial Month an actual date-type column, or is it a string column? If not, you might need to reformat it so that Domo reads it as a date.

I think you can do this with a FIXED function: https://domo-support.domo.com/s/article/4408174643607?language=en_US It always takes me at least three attempts before I correctly write a FIXED function, so this probably won't work out of the box, but it will be something like this: CASE WHEN SUM(CASE WHEN WAREHOUSE_CODE IN…

As an addendum, I think those super wide tables with just a couple rows are hard to scan. To me, it's a lot easier to read across long lists of numbers in columns:

Here's an approach: I think you should group your metrics by 'Revenue' and 'Costs' Then, to get that Total row that is a different aggregation (% gross margin) than your value, a BeastMode that tricks the pivot table into doing that for you: Then a pivot table: One of the options on subtotals is to add padding, which acts…

You should be able to get an average in the total row by switching the aggregation to average the way you did. There's something else going on. Maybe a lot of nulls in the data? Or you accidentally clicked "Hide total" option on the measure?

Okay, I think this is what you'd want for your Test 1 Forecast beastmode: SUM(AVG(`Test`) FIXED(BY Week Ending Date)) - SUM(`Test 1`) That first half sums the average of Test, fixed by week. I use the average so we get 363K once, and then fix it by week so that it uses the average for each week, summing across those weeks.

SUM(DISTINCT) is only adding up the distinct values. In this case, all the values are the same, so it just returns 363K, where you want it to return 363K*4 for the four weeks. Depending on why you are doing a SUM(DISTINCT) rather than a SUM(), you might be able to resolve this by just doing a SUM(). Or you might need a…

Coleman is right that you'll need to share more about your BeastModes to give a full answer, but what what appears to be happening is that you are subtracting the two columns. The first column is unchanging and the second isn't. The resulting grand total is the difference between the unchanging value and the sum of the…