John-Peddle Contributor

This would be the top level of the card, and we'll use a table to drill down to view the repeat offenders in the hopes of finding ways to minimize the issue.

Sorry, was trying to get this done without having to create an ETL but that seemed to be the quickest way to resolve. Went ahead and did just that, so it's all set now though if anyone DOES have thoughts on this please feel free to post so that it's a "quicker fix" if the need arises again in the future. Apologies for…

Hey @rado98, thanks for the reply! We were doing a split and append, and it wasn't working. Since gone back through it step-by-step and through trial & error found where the issue was (the added constants, column combines, and append were ok but we erred in the very first step: column select), and it now works as you…

@Property_Ninja: hey Brian, thanks for the reply! Finally found a link with useful information in Domo University but needed to change search terms to locate it - it's a breakdown of what each action in ETL can do, some with a quick video tutorial, and the one for GROUP BY seemed like what we wanted, as you've provided in…

@ShaneB - just wondering, was the chart type used in the card a table or some type of bar chart where Domo Support was able to create a beast mode that allowed you to show the average in real time, not a decimal/numeric format and minutes as a percentage? Thanks!

@LLucinski, sorry for not replying sooner, but what we were looking for at the time wasn't available, and the work around was to hide the legend, as @ST_-Superman-_ mentioned, but for us that really wasn't an option. 

Stepped back a minute, and realized the issue - using another DIV within the markup when it should've been SPAN instead! Sorry for not seeing that before posting, my mistake. CONCAT ( '<div style="font-size: 28px; width: 100%; height:100%; margin:-20px; padding:20px;">', CONCAT (COUNT(CASE WHEN `Late By` <> '' THEN…

Thanks, @ST_-Superman-_, that was a consideration but the manager requesting this wanted to keep it as negative. I'm hopeful that changing the Min/Max in Value Scale (Line) will provide what they want. As always, appreciate the quick response!

Please disregard, found that changing the Value Scale Lines (i.e. reverse) would provide what we're looking for. Sorry for not playing around with that more before posting!

For anyone interested in this thread, or maybe looking to do something similar in a card: heard back from Domo Support (Joe E.) today, and he was able to create a beast mode that provides an average of two averages within the summary number that works perfectly! This calculation provides us Break & Unscheduled Break,…

@DataJake, sorry for the delayed response but we've been working on another project that took up a lot of time! And again, thanks for all your assistance (as well as everyon else), it's greatly appreciated! Just wanted to respond to your last inquiry in case you see anything in this (screenshots for each): 1) yes, we have…

Jacob (@DataJake), thanks again for your assistance. If we're utilizing the beast mode you provided correctly for our instance (see screenshot), it's still not working for us as it is in your card. Not sure what the issue is, but everyones help is greatly appreciated and we're forwarding this info on to our Engineering…

Yeah, thanks for sharing that @DataJake, sorry for not repying sooner but wasn't able to take a look at this before now. We'll try and revise our beast mode today or later tonight and post here to confirm it works. Again, thanks for taking the time to share this, really appreciate it!

@ST_-Superman-_, tried what you said but that returned a couple different results based on the beast mode used, neither of which was correct. The first was using one of the beast modes you provided earlier, and just making a quick update to multiply by 2; here's what we get: We also attempted to use something more…

@AS, thanks for taking the time to provide beast mode, Aaron; unfortunately we're seeing the same behavior as before, depending on what were setting the Summary Number to: USE CURRENT VALUE again shows 'BREAK' average only, and USE ALL VALUES displays 0.00. Though it wasn't related to a Summary Number, seem to recall a…

@ST_-Superman-_thanks for all your help, as always, it's greatly appreciated! I'll leave this open for now, and double back to post if Domo Support is able to provide a solution for this.

Yes @ST_-Superman-_, always lookin to display the current month for the top level on this card. Sadly, this returns the same "BREAK" only current average when set to USE CURRENT VALUES, and when changing to USE ALL VALUES it zero's out completely. I'd really think that this should be soooooo much easier since it's already…

Good morning, @ST_-Superman-_. Just tried the stacked bar and grouped bar, along with each available measure and the beast modes that have validated but it still just provides the average 'BREAK' time only as it has before, and not a sum of the two. If you have any other suggestions or thoughts on this, please let us know!…

Thanks for the reply, @ST_-Superman-_; tried your suggestion but it seems to return the same as one we used, showing only 'BREAK and not a sum of both as we're looking for. It would seem to be easier to get from within Domo since it's actually providing that sum in the column itself, yet it's proving to be rather difficult…

Thanks, @Valiant, appreciate your reply! Obviously, we can download the existing Box file and attempt to add the column to see what, if anything, happens and revert back if there are issues so I think we'll give it a shot based on your experience with regards to ODBC datasets. As always, thanks for your assistance and…

Thanks, as always, @Valiant, sorted under CHART PROPERTIES>General after adding a dimension in SORTING and we now have order to the chaos previously experienced! Made my day with your quick reply and assistance, it's greatly appreciated...

Thanks @RGranada. Using the updated formula returned the same completion% as the one we're currently using, and we still see that variance when comparing the previous formula (for specific agents only) and only checking them off on the quick filter (with the company-wide beast mode). We're missing something on our end…

@RGranada - the original beast mode formula was to determine Completed Conversion % company wide, as follows: CASE WHEN SUM(`SettledOffers`) = 0 THEN 0 ELSE (SUM(`CompletedOffers`)/ SUM(`SettledOffers`)) END It's a MEASURE being added as a SERIES (Line + Grouped Bar chart), and our Y Axis is the total # of offers company…

Thanks for the response, @RGranada. The formula validates and provides results though they vary when compared to selecting just those agents from the company wide quick filter at the top level, so we'll look into that a bit more on our end unless you have any thoughts on this? And no worries if not, we really…

Thanks for the quick reply, @Valiant. The beast mode validates but once added as a series it returns a different error message this time (a very vague message, so not really sure what the issue might be): "An issue has occurred during processing. We are unable to complete the request at this time." Sorry for…

Thanks so much, @Valiant, forwarding this along to leadership for review in the hopes that we can escalate to our Engineering Team if it's feasible for us! Really appreciate all the help that we get here in the Dojo, and I've been able to learn so much from all the responses to our many questions. Have an awesome day!

@RGranada, before I do anything further, just wanted to see what we should do to expand upon our original request in this thread? Wasn't sure if we should add that in here, or open a new thread since this was already marked as resolved. Thanks in advance!

@RGranada, sorry for taking so long to respond, and thanks for the quick reply, as always! It didn't work at first but then realized SETTLED is a date field and that it likely couldn't be totaled as a SUM, so we changed it to COUNT and it validated - seems to be working as expected!

Thank you both for your assistance! Thought I'd read something previously that stated what your replies indicated but for the life of me couldn't locate that information anywhere in a search, and just wanted to be certain. Have a great day!

Thanks @Godzilla and @Valiant. So basically the beast mode/case statement will go row by row, and in each row once an OR condition is met it will either count 1 or ignore if none exist, amd then move onto the next row and repeat until all rows of data are checked?