Data_Devon Contributor

@DashboardDude - that'd be awesome. I love your content and I always use your "data as ingredients" analogy.

There isn't a native solution for this as you are explaining it. However, using any filter card, the filter label would update and be descriptive of the reporting period filter. There are other work arounds within Beastmodes or Magic ETL, but again, I don't think it's exactly what you are after unfortunately. Did I…

Hello Ankur! A Beastmode might be an unnecessary solution here. You can set the "Geo" (or other categorical data) on the X Axis and the "Count" of a date on your Y Axis. You can then select whatever date you want in the date selection of the Chart itself. This will default the date range for an untouched card. Then, you…

Assuming that you want the column to stay rounded to 2 decimal places, you'll have to convert it to text once you are satisfied with the rounding. Then, upon export, Notepad will recognize it as text (not an integer) so it won't apply any math. Alternatively, you could truncate or trim the integer so that there isn't more…

Onward!! 🚀🚀🚀

VARIABLES!!! Beast of a topic, so I'll defer to Domo's existing knowledge base - see link below. Variables | Overview It's kind of a Beastmode for Beastmodes (BeastModes^2???) This should get you were you want to be - let me know if I misunderstood

I'd use the AddDate() function like so: ADDDATE('2024-12-04', INTERVAL 1 MONTH) If you intend to also jump to the next year - i.e. from December 2024 to January 2025 - that will be an extra step. You can also use the canned "Date Operations" tile in Magic ETL if you want to do it upstream:

I agree with ColemenWilson. You could also try to Cast() the values in a Beastmode to get them to integers/values. Also, could edit it at the ETL level and transform the data column that way. Should be lots of options - keep us posted on what works.

Woohooo!! When will you reveal the speakers?

Good stuff. Thanks for the input khushboo_

Hello Jez! I think you are looking for a "Pivot" type functionality. It sounds like you want to turn (i.e., "pivot") the column names into row names. I can think of two options: Just literally use a pivot table in the "Tables and textboxes" chart type: 2. Transform your data upstream in an ETL using the "Pivot" function.…

@Jessary I still haven't touched Apps and have been able to accomplish everything we need with a normal Dashboard. I agree though, I think the Apps are the faster bigger better cousin of the Dashboard, so once you go App you won't go back. But for those of us living on Dashboards, we can continue because if it ain't broke….

Thank you @MarkSnodgrass and @ArborRose ! I'm glad I'm not alone, and I look forward to exploring more.

I assume that this feature request suggests that it's not possible to bulk-edit this setting? Darn!

I think you'll have to change the "response" to the name of that column, which I think is Disposition. CASE WHEN SUM(`Disposition`= 'Good') = COUNT(*) THEN 'All Good! Omit this person' ELSE 'Mixed Reviews' END I might need an expert to chime in here….

CASE WHEN SUM(response = 'Good') = COUNT(*) THEN 'All Good! Omit this person' ELSE 'Mixed Reviews' What if you did a Beastmode like this ^ and then filtered to only "Mixed Reviews" That Beastmode is looking at the Count of "Good" responses, and comparing it to the Count of total responses. If those counts are equal, then…

I think the native Filter option on Disposition would accomplish this. Drag your disposition column into the "Filter" area in the Analyzer, then select "Good", and change the filter rule to "Not In" Voila! You'll only see responses that are NOT "Good". Is this what you were looking for?

Crap, you are right. I shared the wrong screenshot but I did confirm the actual graph is an overlay. Perhaps I need a different graph altogether? The Green represents a subset of Blue, so the default calculations are faulty because they end up counting green twice… I'll look at Tooltips and I'll explore a different chart…

Yes, I see it there! That is a much better solution anyway. Thank you, as always. Not only did you solve my problem, but you pointed me in an even better direction that I didn't know was possible!! Woohoo!!

Awesome, thank you both! I don't have access to Activity Logs in my Admin portal.. I'll open a ticket and see why mine doesn't show.

We might need more context to be as helpful as possible. What does your data look like? Could you just have one date in one column and another date in the second column, thus allowing comparison between the two?

Outstanding! Thank you both. It worked and the owners that received my analysis were happy. Thanks for everything.

I'd recommend the "Alert" functionality within Domo. From Analyzer, you can format these with the little bell 🔔 icon, or from within the Dataset view you can use the "Alerts" tab. From there, it's a simple interface to set up the alert exactly as you want, what the message is, and who it should go to. For you, you can set…

Awesome, thanks @ColemenWilson. I haven't learned of Variables yet so this will be a fun intro.

@ColemenWilson Thanks a ton! That was a very simple solution, so thanks for helping out. I now have all of our actuals and our budget appended into one gigantic dataset (the hard part). Now, how can I begin to compare budget to actuals with all these rows? I added a constant before the append, so that each row is tagged…

@MichelleH thanks for extra input. That is what I ended up doing - I filteredd out Evals and then I filtered out Surgeries, and then I joined them back in on eachother to get an output that had both on one line.

Thanks @david_cunningham ! That's exactly what I was thinking too, but the Pivot tile in Magic ETL forces you to hard-code each patient ID. (see Screenshot below) With 10,000+ patients, that is not possible. Does that make sense? w

@ColemenWilson Thanks for the response. Excited to make this happen. I've been assigned with creating something like this (see screenshot below). How will appending allow for comparison of the same time periods?

Not knowing the specifics of your join with the ETL, this could likely be from using two columns for the key. The join then will only complete where both keys are satisfied, which will likely lessen the output rows. Therefore, to resolve, find one single unique identifier in the 'gljedtail 2023' that can be joined to the…