DavidChurchman Coach

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

Have you identified that there are matching rows for each side of the join? Sometimes when troubleshooting a frustrating ETL, it's good to start with a very small subset of your full data. Here, you could filter both sides of your join for a value (or handful of values) that you believe should match, create an output for…

In that snip, there are values in the two date filters, which I believe is what is triggering the filter icons. Have you tried clearing those two filters? I don't think you can add any conditions to the filter icons, but you can turn them off for the whole page

For some reason, the styles applied in App Studio don't apply to the card when it is viewed in its expanded/detailed version (hopefully something they correct in the future). You can edit the alternating row colors within the card itself, or just turn them off in the General property settings:

This is not what you're asking for, but for a quick-and-dirty solution, I've starting using the Zoom Workplaces "Clips" to create quick video walkthroughs of my dashboards, and then I upload them directly to the dashboard as a document card so users don't have to go looking for them. (In App Studio, I put it on the last…

It's a little unclear on what you're trying to do, but since your step 1 and 2 are mutually exclusive based on their filters, I think you probably don't want a join, since there won't be any matches to join on. You probably want to combine the data using an "Append" tile instead, which stacks the data on top of itself.

You could round and multiply by 100 in a beastmode. (Not sure how many digits after 0 is useful for you, but probably not more than 2) ROUND(BM DIFF * 100, 2) Then you could edit your notification message to put a % after the values in the email.

I can confirm that I see that too. With no tiered dates, I'm able to select a range of columns: With the tiered dates, I am no longer able to select an area of the chart to filter (a picture showing an absence of a behavior, lol): For how helpful trellises can be in organizing a big chunk of data, there are some…

For #4, I would recommend the 'Split Column' tile, because it lets you keep the "discarded" characters in a separate column, in case you need to reference them later. (You can always drop the extra column using a the "Alter Columns" tile.

I don't think you can concatenate strings across rows using BeastModes, which seems to be the fundamental challenge here. I'm mostly commenting in case I'm wrong and someone posts a way to do that. Depending how many different types of filters you have and how many different product categories, you might be able to create…

I think you could do all of this with no BeastModes or Variables. A variable would be useful if you were trying to do this all with one card, with the ability to switch the metric from MTD, QTD, YTD, but you want to use three different cards, so you can easily define the "graph by" on each card using the date options. I…

%M is for full-month name "June". Try %b for three-letter abbreviated month name. That's as far as I got in checking, but I would double check the rest of your codes, too:

Make your font size bigger and your card shorter. The data table is pretty much fixed in size, but your bars will adjust based on the height of the card.

Not to gatekeep the fun that can be had in Jupyter, as someone that's describing themself as zero-code, I think ETLs and exploring the data with tables is probably a better starting point than trying to learn Python or R to do clustering. Since you said your dataset has hundreds of columns, I would recommend starting by…