Comments
-
🐐🐐🐐🐐 Thank you! (we need a new reaction for the GOATs)
-
@ColemenWilson - yes, I've got dates and times. That should do the trick - but there won't be a set rule for the pre-procedure events. I.e. It could be any number of things that happen before an upgraded procedure, so there won't be a rule that standardizes it. Do you think this will be an issue?
-
I can't figure that one out - so standing by for the GOATs to chime in. 🐐🐐
-
Hi Connor! Using the Scatter Plot, there's a "Grid lines" chart properties that you can edit: In other chart types (pictured below is the Bar chart), there is the same "Grid lines" in Chart properties that will offer the same adjustments - such as removing the Min and Max line, or removing the calculated line: Does that…
-
A deep honor!! 🤝 I'd like to thank my dog for always encouraging me, my ergonomic mouse with side-scroll functionality that lets me easily get to the 329th column, and my team for their outlandish requests that always require new skills to be obtained in Domo. Onward!! ⛷️⛷️⛷️⛷️
-
Hi hollyrene1225. Have you looked into the "Period over Period" chart types? They are mostly plug and play, so you wouldn't need to do any cooking in Magic ETL - just select the chart and you are off to the races. You could also look at a bar chart with a line added - again, mostly plug and play. Is that what you are…
-
Thank you Dashboard Dude! Loved the video. Unfortunately, neither of those is exactly what my Project Manager is after so I'll have to break the bad news to him.
-
You can use the "Filter Rows" tile in Magic ETL to get rid of rows that you don't need.
-
That is a normal pivot added by the upload process to provide helpful Meta data on the underlying dataset - so you didn't do anything wrong! To ensure your ETL still runs as expected - throw a "Select Columns" tile prior to the transforms (upstream) and remove those 2 metadata columns.
-
Hi Kim_Barragan! You can retain those extra columns within the Group By ETL tile that GrantSmith mentioned. Just "Add All Columns" in Step 1 of that Group By tile, or select the specific columns that you mentioned. This should retain the columns you need downstream, but also create the group by that you were originally…
-
Hello, and welcome to the community! I trust you'll feel supported and encouraged as you delve into the Domosphere. I like to use "Filters" card types that are placed in a logical space around the table that will reflect the applied filters. The "Dropdown selector" will be perfect for your use case. You can create a table,…
-
Thank you both for the theory and the practicality in this.
-
@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?