DavidChurchman Coach

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:

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: In the meantime, I also recommend this recent discussion, which has some ideas on alternatives/different ways to use bullets:…

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…

There are the Domo University courses, which will have a lot of examples of how to apply everything in Domo. The only caveat is I feel like most of the Domo courses assume your data is already structured relatively cleanly, maybe coming in from system. For a theoretical grounding on how to structure your data from the…

I have done group bys on similarly large data without a problem. Here are a couple suggestions for debugging: Create an Output Tile directly from the GroupBy in your full dataset to see if it's blank before you rejoin it back to the data. (You can delete it later). Double check that there's only one value for your test ID.…

For the original question, I have done something like this using a BeastMode as a card filter for every card on the page, filtering for 'Include': CASE WHEN Text_Variable IS NULL THEN 'Include' WHEN Text_Variable = 'Default Text' THEN 'Include' WHEN LOWER(Description) LIKE CONCAT('%', LOWER(Text_Variable), '%' ) then…

@brycec LISTAGG is a new one for me, thank you! I played with it, and it also works with DISTINCT, so I'll add that to your suggestion: REPLACE(LISTAGG(DISTINCT `Current Pages), ',', ', ')

I don't think you can enforce a naming pattern when people are creating the dashboards, but you could use the DomoStats datasets to check your names against a pattern. You could set an alert that sends you (or everyone, for some good public shaming) an email every time someone creates a new app/dash that violates your…

One other place you can add text from fields is in the summary number. Nice thing about the summary number is you can apply HTML formatting (or not) with a BeastMode. There are some kind of ugly examples of that here, but you get the idea: One thing that is impossible in a BeastMode (as far as I know) is to reference…

1) I don't think that it's this BeastMode that's causing the data to split across columns, since you're summing it. It's probably the TEST column, which I assume is the same one as this discussion: To quote myself from that discussion: "One note of caution is that your current set-up won't work if you have multiple…

And just like that, she was gone. The stock model with chunky glasses staring contentedly at her phone is no more. Now, I kind of miss her. I guess you don't know what you have until it's gone.

You can schedule cards or dashboards as reports that are emailed to people from Domo. If you wanted to automate it, you could create the dashboard using the DomoStats data, and create tables of things like "Dashboards created this month" or you could just make something manual with text cards that you schedule to go out…

Yes, I would love more flexibility for reference lines. Here's another idea that fleshes that out even more, if you want to add votes to that one as well:

Your script uses the OpenCage API, so that's what I tested:

Be careful: both the address you were searching for and your API key are in that error code. Using your API key, I got the same 401 error as you. Using a valid API key and your exact same script, I was able to retrieve coordinates. I would double check your API key one more time.