DavidChurchman Coach

I think the easiest/cleanest option is you can use a stacked bar chart and then use trellis categories to group your stacks. I might also suggest with the set-up you're describing to instead just do a stack of 4 categories: New*US; New*Non-US; Existing*US; Existing*Non-US. Then you could use color coding/sorting, to…

I'm assuming your source data looks like this. (Per @ArborRose's suggestion, it's always helpful to provide an example of the structure of your raw data, not just the desired report). Assuming that I'm correct about the raw data, this would be easy to replicate in a Pivot Table, using this BeastMode for % of Revenue:…

Yes, you can use HTML tags on custom summary numbers to change the style. Something like this: CONCAT( '<div style=color:#3a8dde; font-size:10px; font-weight:100>', Your current Summary Number BeastMode, '</div>' ) More examples here: And a list of the available style tags are at the bottom of this article:

Yes, that would be helpful. Even better would be to be able to draw values from a column or table so variables could be more dynamic.

Does your expected variance really change going out it into the future? If instead of having changing variance, you picked a static expected variance, you could use the compound interest formula to project it out without doing it recursively. Let's say your expected variance was 4%:…

You could also use a fixed function to do this. Something like this: SUM(AVG(`cost`) FIXED(BY code))

Instead of a DISTINCT, use a FIXED function. Something like this should work: SUM(SUM(`TOTAL Customer PTS`) FIXED(BY Customer)) I bookmarked this KB article my first year of using Domo because I used it so often: https://domo-support.domo.com/s/article/4408174643607?language=en_US

Sadly, no, not out of the box. You cannot color anything in Domo based on a different field. There is an idea similar to this posted in the idea exchange basically every month. Here's one, so feel free to upvote it (and the many others) or add your own idea to the void: Some options in the meantime: You can add a second…

In a stacked bar chart, You can use "percent to target" as your value so they're all on the same scale, and then a tool-tip as your label where you have the actual values. For color coding, use a series. I manually created the labels in the data, but you could do that more dynamically with some concat() and case statements.

Also, in MagicETL, you could use a scripting tile to use R or Python to do this with a for-loop, but if you go that route, it would probably be easier to use a built in function like cut() from R or pandas.cut().

OP asked if you could use a variable, so to add to @GrantSmith's answer, you could replace every 5 in his answer with a variable (let's say it has a default value of 5) and then dynamically adjust the bucket size on your dashboard with a variable control.

Yes, agree it would be better if there were some styling options built into the interface, and underlining is not one of the supported HTML tags. That said, the conditional formatting enabled by HTML can be more useful than underlining, etc. If I had to choose, I'd choose the ability to use HTML tags with conditional logic…

Nothing wrong with Colemen's formula, but since you already created a table that you joined on your start dates, you should be able to use that same table and join it a second time to your end dates. Also, for a BeastMode friendly formula approach, you could leverage the WEEKDAY function, which returns 1 for Sunday, 2 for…

You can't do it with HTML tags, but you could play with concatenating white space to the front of the summary number if you have a fixed width card.

Agree with chart title formatting. FYI: @JasonAltenburg you can format summary numbers using HTML tags: KB article:

For the card not to even update in the Analyzer, I would guess that it's not actually being fed by the same dataset, just one with the same name. When you click the down arrow next to the dataset and select "Change Dataset", is there more than one option with that name? My hypothesis: someone was working on the MagicETL,…

There is a DomoStats for Workflows.

It looks like Delivered Margin Define is coming from a different BeastMode. What does that BeastMode look like? It is probably the culprit.

Ah, I didn't test role changes. In the DomoStats Activity log, you can see "CHANGED_ROLE" and the "Object_ID" corresponds to the person whose role was changed. You can join that to the People DomoStats to see the person and their current role, but not what the role was changed from, which I'm guess is what you're after? If…

In the "Activity Log" report from DomoStats, I don't get that exact field, but all of the information contained in that field are in it, split across columns. You could probably recreate that field without too much trouble: CONCAT(`Name`, ' ' , lower(`Action`), ' ', case when Object_Type = 'DATA_APP_VIEW' then 'app' … end,…

Jay.p is talking about clicking/unclicking the legend to filter the card. I also see this behavior when viewing the "detailed" version of the card (not just on bubble charts, either). If people are looking at this card in the "detailed view", you could add your series as a "quick filter", which will always appear in that…

Agreed. Here's the same idea, with a comment from Domo that it is in the backlog (over a year ago). Add some votes to that idea, too, to bump it, as well as this one.…

I like ArborRose's regex for cleaning the notes, but then the second part seems too manual, especially if you have a large number of company names. If you have a list of clean names, you could join with an expression to see if those clean names are like the clean notes. WHEN clean_notes LIKE concat('%', clean_names, '%')…

A little clunkier than multi-select on a filter, but you could achieve this with multiple variable controls. Let's say you want them to be able to select up to 3 Job types, you'd create 3 variables: selection_1 selection_2 selection_3 Then create a BeastMode that references the variables and use that BeastMode as your card…

I don't think you can control the color of the variance lines, since it's not a series or variable, but something calculated on the backend. If you used the Symbols+Bar type, you could change your starting symbol and use the color rules, but it wouldn't calculate variance for you. You'd have to figure out how to calculate…

Glad it helped. One note of caution: the problem with using BeastMode rather than ETL to force your data wide is it doesn't actually change structure of the data, just relabels it. Prior year data are still on different rows than current years. So if you try to do anything with your date variable, like filter it or…

I think I'm going to suggest something similar (identical?) to GrantSmith, but maybe easier because instead of flexible periods, it's just YoY. Instead of a long dataset feeding your card that has all of your dates on top of each other, you can restructure your data to use just this year's data, with additional columns for…

Yes! I think this problem is compounded by the fact that you can't control the organization of App Studio Apps, so the only thing you have is the name, and the name has to be super-short, so it would be difficult to add a descriptive prefix to apps you wanted to be grouped together. This was my idea coming at the same…

I'd add that the low display resolution on text cards makes them hard to read, as does the default font option. When exported as PPT/PDF, they're especially hard to read and ugly.

You could pivot your data to be longer, and make the "column" field be your metric name. Filter for non-blank values and your column headers will be dynamic to what data is available.