DavidChurchman Contributor

You could use Origin as the 'Series for Color' in the Lat/Long map. This would tie the origins to their destinations, so when you hover on an origin, all the destinations would appear, and you could click to filter by that series. You'd want to restructure your data a bit. In a magicETL, you could select all of your origin…

Michelle's suggestion is good, but the bullet chart is designed for this type of situation. You could create BeastModes for each range, per Michelle's suggestion, and then use them as the different target ranges on your card (range 1, range 2, etc.). "Worked Hours" would be the same color throughout the chart, but would…

Is there any kind of grouping that would be useful? I find with large tables, it's helpful to start with a grouping variable and check off "show sub-total rows", which allows you to collapse the groups and help them navigate more quickly around the table by expanding/collapsing those groups. My understanding of 'dynamic…

Similar to what you're saying, you could use an ETL to restructure your data to something like: Type Index | Description | Month | Actual/Budget/Variance | Amount To do that, you could: split your dataset using two filter tiles into actual and budget Join them back together on Type/description/month Use a formula tile to…

The forecasting chart has fields where you can plug in lower/upper bounds of forecasts. KB article on forecasting chart

You can add multiple conditions to a filter tile, then there is the option of "all" or "any" of the rules to be true. Basically, logical "AND" or logical "OR". If it's more complex than that, you can create a "formula rule" within the filter tile. KB article about filter formula

Depending on the setup of the card/data, I think you should be able to change the Beastmode to just COUNT(DISTINCT EMPLOYEE_ID), add it as a Tooltip so that it's at the right level of aggregation and then use it as a filter.

A possible approach: what if you appended department-level copies of the dataset to the bottom of the dataset? Then you could give departments access to their rows via PDP and the default filter could be for single-select filter for "View my department only" or "All data". You would just have to be careful that if they…

The Total is your "Hover Legend". When you're not hovering, it shows the total, when you are, it gives details around the slice you're hovering over. You can choose the option to hide the hover legend to remove it. The reason it's showing in the graphs on the right but not the left is they are sized a little smaller. A…

That's a bit different. It's not a simple sum, but the sum of the max value by user. That would require a fixed function () that could look like this: sum(max(number) fixed(by id)) You could still either make 3 cards or create a variable that allows a user to flip between the 3 levels of aggregation.

Maybe you could create a filter on a BeastMode like this, assuming you don't have negatives that would make it inadvertently add up to 0: CASE WHEN SUM([All those value columns]) FIXED(BY [All those row columns]) = 0 THEN 'Exclude' ELSE 'Include END You could wrap all your value columns in an absolute value or square them…

I frequently encounter problems when filtering/sorting columns with null values. Marks' suggestion is good, because it will give you a column with no nulls.

In addition to Mark's suggestion of turning on the 'Show Current Date' line, you can also calculate your percent complete to always be up to today's date, like: case when DATEDIFF(CURRENT_DATE(),Start Date) / DATEDIFF(End Date,Start Date) > 1 then 1 else DATEDIFF(CURRENT_DATE(),Start Date) / DATEDIFF(End Date,Start Date)…

Not totally the same, but you can do this with a filter view.

Assuming by row, you mean everything that will display as a row in the pivot table and not a row from your original dataset. If that assumption is correct, then the 0s will be all the values associated with what defines your rows and columns With that in mind, the BeastMode GrantSmith mentioned above would need to be a…

First, how to get those aggregations (no formula needed): You could set up a table card with two columns, id and number . If you select "sum" for the aggregation for that field, it will show the sum per id. Then you could have a second table card with list and number and a third with just number. To match your question, I…

There is "Domo Everywhere", where you can privately embed instances of your dashboard somewhere outside of Domo, and it is possible to create your own authentication with that private embed (i.e. not a Domo account). Using Domo Everywhere does cost more and there are technical hurdles to implementing it. PDP is not…

In MagicETL, you could do outer joins between your actuals and scenarios. If you want all scenarios available for both the first and second filter, then you could join the scenarios twice, renaming the columns on the join to distinguish. So basically Actuals x Scenarios copy 1 x Scenarios copy 2. Then you could do all the…

I would use a "bullet chart" for this situation. It's designed to show progress against a goal with staggered targets.

I haven't used PyDomo, but it sounds like you're replacing a dataset when you want to append your dataset. This post has the same question:

I think a best practice when dealing with a large number of fields like this is to unpivot them into a "long format" dataset rather than a super wide dataset. That helps you not have to perform the same transforms 25 times, and usually makes building cards easier, too. Making some broad assumptions without knowing your…

I was having a similar issue with a date column that changed to text when I wrote the data frame to a dataset in Domo. I played with the different dtypes, and found one that did stay as a date after moving to Domo (though the timezone changed, so it ended up being a few hours different than what I had in Pandas). Domo…

I believe the controls match the sort of the dataset or card.

To do aggregate (as opposed to row-level) calculations in a BeastMode, you'll need to use FIXED functions: Yours would be something like: (case when sum(count(Distinct `Customer Name`) fixed())>=2 then 1 else 0 END)/sum(count(distinct `Customer Name`) fixed())

I think there's more than one thing going on, but I would start by playing with your sorts. I don't think you want a sort on Onboarding Conversion status, which is what's causing the duplicate dates across your x-axis.