DavidChurchman Coach

The Total is your "Hover Legend". When you're not hovering, it shows the total, when you are, it gives details around the slice you're hovering over. You can choose the option to hide the hover legend to remove it. The reason it's showing in the graphs on the right but not the left is they are sized a little smaller. A…

That's a bit different. It's not a simple sum, but the sum of the max value by user. That would require a fixed function () that could look like this: sum(max(number) fixed(by id)) You could still either make 3 cards or create a variable that allows a user to flip between the 3 levels of aggregation.

Maybe you could create a filter on a BeastMode like this, assuming you don't have negatives that would make it inadvertently add up to 0: CASE WHEN SUM([All those value columns]) FIXED(BY [All those row columns]) = 0 THEN 'Exclude' ELSE 'Include END You could wrap all your value columns in an absolute value or square them…

I frequently encounter problems when filtering/sorting columns with null values. Marks' suggestion is good, because it will give you a column with no nulls.

In addition to Mark's suggestion of turning on the 'Show Current Date' line, you can also calculate your percent complete to always be up to today's date, like: case when DATEDIFF(CURRENT_DATE(),Start Date) / DATEDIFF(End Date,Start Date) > 1 then 1 else DATEDIFF(CURRENT_DATE(),Start Date) / DATEDIFF(End Date,Start Date)…

Not totally the same, but you can do this with a filter view.

Assuming by row, you mean everything that will display as a row in the pivot table and not a row from your original dataset. If that assumption is correct, then the 0s will be all the values associated with what defines your rows and columns With that in mind, the BeastMode GrantSmith mentioned above would need to be a…

First, how to get those aggregations (no formula needed): You could set up a table card with two columns, id and number . If you select "sum" for the aggregation for that field, it will show the sum per id. Then you could have a second table card with list and number and a third with just number. To match your question, I…

There is "Domo Everywhere", where you can privately embed instances of your dashboard somewhere outside of Domo, and it is possible to create your own authentication with that private embed (i.e. not a Domo account). Using Domo Everywhere does cost more and there are technical hurdles to implementing it. PDP is not…

In MagicETL, you could do outer joins between your actuals and scenarios. If you want all scenarios available for both the first and second filter, then you could join the scenarios twice, renaming the columns on the join to distinguish. So basically Actuals x Scenarios copy 1 x Scenarios copy 2. Then you could do all the…

I would use a "bullet chart" for this situation. It's designed to show progress against a goal with staggered targets.

I haven't used PyDomo, but it sounds like you're replacing a dataset when you want to append your dataset. This post has the same question:

I think a best practice when dealing with a large number of fields like this is to unpivot them into a "long format" dataset rather than a super wide dataset. That helps you not have to perform the same transforms 25 times, and usually makes building cards easier, too. Making some broad assumptions without knowing your…

I was having a similar issue with a date column that changed to text when I wrote the data frame to a dataset in Domo. I played with the different dtypes, and found one that did stay as a date after moving to Domo (though the timezone changed, so it ended up being a few hours different than what I had in Pandas). Domo…

I believe the controls match the sort of the dataset or card.

To do aggregate (as opposed to row-level) calculations in a BeastMode, you'll need to use FIXED functions: Yours would be something like: (case when sum(count(Distinct `Customer Name`) fixed())>=2 then 1 else 0 END)/sum(count(distinct `Customer Name`) fixed())

To some extent, it is implemented, but costs extra. There are limitations to where the custom fonts can appear: https://domo-support.domo.com/s/article/5428851518999?language=en_US

One of the simplest things that would open up so many options

Strongly agree with conditional color formatting. The custom color templates aligned with your company is a available in the "Brand Kit", for 💰💰💰 https://domo-support.domo.com/s/article/5428851518999?language=en_US

A lot of what you're describing can be done with bullet charts. It has that satisfying goal line for the bar to punch through, as well the ability to shade incremental goals in the background before the one big goal. You can't break it up into a stacked series, but I think you would end up with something easier to…

Yes, agreed! The export should appear the same as the dashboard for both PDFs and PowerPoints

I think there's more than one thing going on, but I would start by playing with your sorts. I don't think you want a sort on Onboarding Conversion status, which is what's causing the duplicate dates across your x-axis.

There are no rank functions in beastmode (unless I'm mistaken?) but this would be relatively easy to accomplish in Magic ETL. First, a GROUP BY block, grouping by CPT Code, getting a sum of value. Second, a RANK & WINDOW block, finding the descending rank of the value sum column you made in your group by. Third, LEFT JOIN…

Originally, I thought it was because my chart had two many nodes, but even after restructuring so I only have 2 nodes, it's still cutting off the right side of my chart

I'm noticing this, too. Updating the variable definition in the analyzer does not update the variable control card. This needs to be fixed to make variables usable

Okay, I figured out the actual solution (can I revoke marking someone's answer as the solution and give it to myself?). Maybe this would be obvious to everyone else, but in case you are like me and have huge bubbles you can't figure out that don't correspond to your legend, this is what I needed to do: * Turn off auto-zoom…

Here's an example Magic ETL that does this: This creates a column that has the Total # Accounts on every row You can then use the average of that as your denominator in the BeastMode: COUNT(DISTINCT `Account Number`)/avg(`Total # Accounts`)

The image given in the documentation looks as if it the legend is scaled correctly, or at least in the correct ballpark. Bern is 15.6 million, which appears to be almost exactly the same size indicated in the legend. Based on this answer, this is either misleading or incorrect.

It sounds like you want to do a left join using either DataFusion/Blend or Magic ETL. Based on your question, it's a little unclear what you want to keep from the first dataset and what you want to drop, but both options give you the ability to drop columns from either the left or right dataset.

I would like this for choosing which elements appear on the card (title/description/summary, etc.) I often want a similar layout for 3-6 cards at a time