DavidChurchman Coach

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.

Bumping this, because the email function is now live, but I'm curious about additional export options

IMO ideally you should not use to color to encode a variable with more than 5-6 options, and even in your 8 question example, it looks like you have around 20ish response choices? To give good feedback, it would be helpful to know what you want the user to get out of this chart. I'll give some suggestions based on what you…

There's a checkbox to apply the color rules to totals and subtotals in the "general" section of chart properties:

This is something that comes up in the forum all the time, and 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…

Oh, I didn't know that shortcut! I usually just Google something like "unicode triangle down" and copy/paste from the web… inefficient but effective

There's an idea you should upvote to make this easier: https://community-forums.domo.com/main/discussion/56705/scroll-bar-in-bar-charts?utm_source=community-search&utm_medium=organic-search&utm_term=scroll+bar+chart And a similar conversation: https://community-forums.domo.com/main/discussion/comment/100948#Comment_100948

To get an answer, I recommend you break up this question and ask just the first part. If you're still stuck after that, ask the next part. There's a lot going on and it's not clear what you're asking. At the end of your question, it seems like you're asking about why your sums aren't aligned 38K vs. 34K. I'm not sure how…

I feel like there's an idea requesting folder-style organization about once a month (whether it's for datasets, dataflows, apps, pages, etc.). Below I'm listing some of those that are most similar to your idea to show that even though most of these only have a few votes, collectively they show it is a big enough issue that…

More built in options are always nice, but this can also be achieved using a BeastMode in the sort

I count 6 of these: ( and 7 of these: ) If that's not it, then can you give more details about what's not working? Is the formula validating, but not giving the expected result? Or is it not validating at all?

Most of the idea links go to the wrong idea

You need to write a BeastMode for your Y-axis to format it all as percentages. It will probably be something like: sum(Aloc..)/Sum(SUM(Aloc..) FIXED())

Apply the color rules to all cards. Then any cards that are special cases, "apply color rules to only this card". That will not remove the color rules from the other cards.

I think instead of bringing in the total and selecting the 'percent_of_total' label, you'd need to calculate the percent of total first, and use that as the value. Then your totals would appear correctly.

Can we see your BeastModes? I suspect there is some difference in how the two bars are aggregating giving them a hard time combining. Another (less likely) guess is something is off with the sort. Try adding date to your sort to see if that does anything.

When you have a series, you can add a global-average line using the "Scale Marker" in the properties.

Yeah, you should dynamic unpivot the data in MagicETL. If that's not an option, you could color code 0s to be gray to de-emphasize them, which is another way to make sparse tables more readable. (Use black with 100% transparency and select the lighter color font).

Yeah, I want to be able to do this, too, and posted this idea about it. Upvote/comment on it to keep it in the running, because it didn't get much love: https://community-forums.domo.com/main/discussion/61581/bullet-chart-additions-trellis-choose-which-data-labels In the meantime, I also recommend this recent discussion,…

With your sample data, I think this does what you were asking for: Create a control variable: Create a beastmode reference your variable (when YTD, finding the cumulative sum by year, else find the regular sum): Add the variable control and you should be able to toggle between MTD and YTD calculations:

It would be helpful to have a dummy sample of your data, because you're throwing me off by saying you have a column for 2023, 2024, and 2025 values. That sounds like a wide dataset, but then you have a single date column, which sounds like long data. I'm going to assume your data is long and that those year columns are…

It's really hard to get partition or fixed functions to play well with a Pivot Table. You could create something that checks against an input variable, where the user can input which week they want to calculate BOH with (less automatic then what you were exploring): case when Week ending date >= date(Date Input Variable)…

Or a shift-click functionality that allows you to select multiple columns and drag them all at the same time

With that OVER() clause in your CASE statement, it's producing a value for each week that can't be combined. If you have the week as part of the Row/Column definition, then you're fine. If you don't, then there are collisions. The way your function is written will always give 0s to everything besides this week, so is there…