david_cunningham Coach

Hi @DWill978 - as far as I know there isn't a way to drill to a specific path dependent on which column is clicked using Domo's out of the box features. I'm curious to hear if any other community members know of a way to do this though. I'm guessing there might be a way with a brick or a custom-app, but that is a lot more…

@user04612 you could use the Domo provided running total line or bar chart cards. There is also a setting in Bar/Line charts to create running totals. You can find this in General > Number of Running Total Lines. If neither of these options work for you. Please let me know and I can help you create a beast mode.

@kim_barragan0126 If it’s always just the 2 columns, and you will have nulls. You could do (col1+col2)/2

@damen please post the code you are using.

@damen wrap it in CONCAT() and then adjust your year Concat(year(date issued), ‘-‘, year(date_add(date issued, interval 3 year)))

@Zofia here you go! The way this works is that we compare the month and year of the date to the month/year of the current date. We use date_add to add a month. This should work across year changes as well. CASE WHEN MONTH(CURRENT_DATE()) = MONTH(date) and YEAR(CURRENT_DATE()) = YEAR(date) then 'Show' WHEN…

@tmerchant I just tried your beast mode using some sample data, and didn't run into the same error. With that being said, one thing I would recommend is to break your beast mode into parts, and test those parts to figure out where the problem is originating from. For example, take SUM(CASE WHEN Category = 'Revenue' AND…

Thank you @ColemenWilson! I'm thrilled to join you, and the rest of the coaches - y'all are a talented group! 😁 Looking forward to continuing to learn and grow together!

Hey @RobRolek, thanks! 😁

Thanks @JasonAltenburg ! 😁

@TMonty0319 here is how you could do this in a beast mode. Lag will default to the last available date. For example you can see that this dataset skips days, but the beast mode still shows the data from the last available date. (LAG(SUM(day_tank_value),1) over (order by date asc) + LAG(SUM(oil_added_tank),1) over (order by…

Keep in mind this is not a fully fleshed out solution, but does work if you are just looking at general trends. Depends how exact you want/need to be in your weekly average. But one possible solution is to graph by month, and then have a beast mode like this. SUM(value)*12/52 This is likely better than just dividing by 4.…

@AngelaO415 sure, here you go. SUM(SUM(case when requests_state in ('granted','closed') then requests_amount_recommended end)) over (partition by organizations_name)

@AngelaO415 are you summing by both requests_amount_recommended and your new beast mode? The same beast mode will work in a table. I can't tell from your screenshot what's really going on. But in the below example, I'm using a table, and you can see that there is no repeat organization_name, and both fields are summed.…

@AngelaO415 - here you go. You would use this beast mode as the input to your y-axis if you are using a bar chart. case when requests_state in ('granted','closed') then requests_amount_recommended end

+1 to this. Would love the ability to exclude certain users from the result set.

@Chris_Wolman this is great to know! Thanks for sharing 😁

Yes - you can use the Rank and Window tile to create a rank based on your id. Then use the filter tile to return the rank you want. If you want the min id you can just sort ascending on your rank/window function and then filter to where rank=1. If you want the max id, you can sort descending and then filter to where…

@Caua_Soares you could achieve that in a table by creating a beast mode where you concat together your symbol and the amount. This does complicate things a bit though, because you would have to format the amount in your beast mode instead of relying on Domo's built in number formatter.

@jrtomici the answer provided by @ColemenWilson is the correct one, and I kindly ask that you please select his answer as the best response. I just wanted to provide you with a quick breakdown of how to achieve it. Example Data You'll use the dynamic unpivot tile, selecting "Name" to not be pivoted and then assigning…

If you have a lot of different combinations and don't want to do this manually, an option is to do it in ETL with REGEXP_REPLACE. REGEXP_REPLACE(string, '^.(\d).$', '$1')*1

@random_user_098765 here is an example of how I typically do it. You can swap out the font size to get different results. CONCAT('<font size="3">Medium Text ',SUM(Order Item),'</font>') For example Something to keep in mind is that this will only work in the web-app. Summary numbers in the mobile app won't change.

@Cfunk here you go. A couple of issues with your original beast mode. You needed to wrap your date string inside of DATE() to convert from string type to date type. IFNULL() requires 2 arguments, something to check if null, and a replacement string. Updated Beast Mode CASE WHEN Registration Date < DATE('2021-06-22') then…

Good catch @MichelleH! @Strongreece my comment on preview sometimes not showing rows in MagicETL when you are dealing with large datasets and a small result set still stands, but Michelle's answer should be selected as the correct solution to your post.

there’s 658 out of almost 3.5 million rows that meet that criteria. Preview doesn’t process all rows, just the first 10k up to 400k. One way to test if this filter is working as expected is to attach an output dataset (“test filter”) and execute the dataflow. If the output matches, you know you are good to go.

I'd be happy to try to help you, but I'm not sure I understand what you're trying to achieve. Can you please do a quick mock up of your desired summary number output along with some example data? I can then take a look for you to figure out what's going on.

For workbench, the easiest thing to do would be to make use of the TOP/LIMIT functionality in your SQL statement. This wouldn't cause the job to error out, but you could limit the number of rows that are processed/stored in Domo.

Is Donors a numeric field and is it being stored as such? Are you aggregating any of your fields? Please post some screenshots of your dataset and output so that I can try to figure out what's going on. For example - you can see below that the logic is working as intended. case when value < lower_bound or value >…

Are you trying to get an average weekly count by action? In other words. Week1: 25 Week2: 50 Week3: 40 Week4: 45 = Total of 160 / 4 = weekly average of 40. Just trying to clarify what you are looking to achieve before diving in on a solution.

The best resource is the Beast Mode KB article. Another thing that I will sometimes do is to check the functions that work in ETL. Not all of them cross over to Beast Mode, but some do that are not listed in the Beast Mode function list in Analyzer. For example SUBSTRING_INDEX(). Lastly, beast modes are based on MySQL.…