DavidChurchman Coach

You can't directly. You could change your measure to be "change from prior month" instead of the raw value. You could have that "change from prior month" as a separate value in the pivot table, and color-code that A different approach I've used is concatenating an icon in the formula. I showed a (not particularly…

With just 6 values (Marge/Revenue/Cost and their respective budgets), I think a visual that doesn't require interaction would be preferable to let users see measures at a glance. A bullet chart could do that, and then I would use a different series for budget vs. target to make clear you're trying to push through the…

If green is a subset of blue, I think the overlay bar is the appropriate graph. The advantage of the overlay is that even without figuring out the percent that you want, the raw values will be correct, so hovering and tips will work out of the box. The default calculation for percent_of_category isn't necessarily wrong, it…

First, I don't think that's an overlay bar, because there's no option label totals in an overlay bar. But if you were using an overlay bar, MichelleH is right that the best approach would be a BeastMode and a tooltip. It's an unusual percentage to get, but I think if you're using an overlay, I agree, it's what you want.…

The label options on boxplots make them essentially useless, IMO. You can't even position them in the correct location (i.e. median goes on the median). You could concatenate the N to the axis labels. Something like this: Disadvantage is changing the names of the series makes cross-filtering between cards dice-ier. I would…

Ideally, your data would look like this: Category Type Value Budget Planned 343 Budget Carry-over 3432 … The easiest way to get it in that format is with MagicETL. There's probably a more elegant way to do it with a dynamic unpivot, but to me, the easiest to understand is to just select the two columns, add a category…

You need to tell the tile what you want it to output: write_dataframe(unique_account_count_cumulative) I also think you want to unindent your current last line to take it out of the loop, otherwise you're unnecessarily over-writing the same dataframe over and over.

Unpivoting the taxable/untaxable would be helpful. The sunburst chart is helpful for breaking out a pie-chart into subcategories, with helpful default tooltips aligned to what you want: A treemap is also nice for showing subcategories. One disadvantage of the sunuburst is the area of the sub-categories is too visually big…

I think Arbor's solution is probably best. If you want a 0 BeastMode approach: If you have some ID row, then after filtering out the keyword you want, select-all on that ID row. Then clear your keyword filter, and it should still only be the rows without that keyword. Then you can apply a second keyword filter.

You could do this with no Beastmodes by playing with the date range, "graph by" and "compare to" in any of "Period over Period" charts.

Sankey charts are powered by "From", "To" and "Value" columns. For your example, you'd probably have something like: From To Value Node 1 Node 2 10 Node 1 Node 2 10 Node 2 Node 10

I think the case statement is going to have a hard time when the level of aggregation is different for the different clauses. Maybe I'm still not fully understanding your data, but do you really need the partition? If the goal is just repeating every time, then just a straight average would still work, right? case when…

If the data is long in the way I structured my example (one column has both actual values and goal values), then not really. You could create a separate card with monthly totals, and include the same symbol in the data labels. (I recommend a bullet chart to show meeting the goal visually by month). If the data is wide, as…

IMO, you wouldn't want 4 separate lines because it's all the same cases, so splitting them into four would be misleading. You could concatenate the four time zones into a single axis label. Like: CONCAT(`Hour`, '|', CST,'|', MST,'|', PST) And then your x-axis would have labels like: 0|23|22|21 1|0|23|22 2|1|0|23 Or maybe a…

Yeah, I would love an out-of-the-box solution for this. Some possible options. Collapse into one column, "Actual - Goal" and color code that instead: sum(case when Measure= 'Actual' then Value end) Fixed(by ID, Month) - sum(case when Measure= 'Goal' then Value end) fixed(by ID, Month) 2. Concatenate an icon to your value…

I would push this one step further and allow users to manually specify the label color on a series. It could be the same menu/options as "Table Text", although even better would be the option to pick your own color.

What is the termination date for active users? If it's null, then it looks like you would be dividing by 0, because no active users would have a term date the same as this year. Do you even need to check the termination date of active users, since I assume the definition of active users is that they are still there this…

I can confirm that it seems weird that you can't control the hover text for the sunburst.

Yes, this is the "DataFlow Input DataSource" report in DomoStats. (this reports out dataflow IDs and datasource IDs, so if you need their names, you'd need to join it with other DomoStats reports). Once you've determined the impact, depending on the type of data, you can probably change the input table within the setting…

In the "Page settings" of each page, you can use an "image fill" for the background for each individual page.

The first table doesn't require an ETL, a fixed function or a distinct function. This is the exact kind of data Domo tends to works best with. This BM should work: case when sum(PlannedCost)<sum(ForecastCost) then 'Over' when sum(PlannedCost)>sum(ForecastCost) then 'Under' END However, the second table, where you get…

I would start with the documentation for variables, which does have a video: The variables controls are similar to filters, in that they enable users to manipulate how the data is presented. They are different in that they are not changing which rows of data are being presented, but in my example, in what columns are being…

I would add that the behavior when they do appear should be to calculated by facet, not overall.

There are a lot of approaches you could use to do this. I can't tell what level of aggregation you'd like, so if all you're looking for is just overall proficiency by subject, you could create a handful of summary number cards that averages each of those. If you want the ability to summarize by different levels of…

Personally, I would use MagicETL to unpivot the data to be this structure: Order | ID # | ID 111 | ID 1 | 1 111 | ID 2 | 7 112 | ID 1 | 2 112 | ID 2 | 6 That would make counting the IDs trivial in the card, and you can pivot by ID # to get the same table. If you can't use MagicETL, then depending on the structure of your…

In App Studio, you can create card styles where you can adjust the amount that corners are rounded. (Can't do this in a standard dashboard). I don't have any experience with this, but I know at the card level, you can edit JS/HTML/CSS using bricks from the Domo Appstore.

Open the card in Analyzer, and make sure the "Properties" menu is selected, and it should appear under your Filers/Sorting menus.

The preview is limited to the first certain number of rows of data, so if there are no matches at the top of the inputs, it might not find any data to preview after the join, just give you a green check if it's a logically sound join.

Case Date Selector is a Variable (as opposed to a Column in the data), then that first card in your picture isn't really a filter, but a Control. There are fewer options with a Control than for a filter. With a filter card, you can edit the actions to only apply the filter to certain cards, in which case you could adjust…

This is something that comes up in the forum all the time, and I'm sure I've seen multiple ideas posted about it. Posting it again will probably help, but also comment/upvote these. These were just the ones I could find with a quick search. If there are others, please add them in the comments