Valiant Coach

I'm fairly certain you'll need to calculate the Next City ahead of time. You could accomplish this by doing the following: Transform 1: SELECT MIN(CASE WHEN `ClosingDate` > CURDATE() THEN `ClosingDate` END) AS 'MinDate' FROM Dataset Transform 2: SELECT CONCAT('Next City: ', a.City) AS 'NextUp' FROM Dataset AS a INNER JOIN…

Any difference if you made it? SUM(`Group Hours`)/SUM(`Group Leads`)

Vikrant, Unfortunately you can't do this as a beast mode. You can however do this ahead of time in an SQL transform. Here's the instructions on how to do this: https://knowledge.domo.com/Prepare/DataFlow_Tips_and_Tricks/Creating_a_Rank_or_Row_Count Best of luck, Valiant

With large datasets, I normally have more luck (where speed is concerned) using the ETL tool. You could accomplish what you're looking for using 3 widgets, Input Dataset into Filter Rows into Output Dataset. On the filter rows, just select the row you want to filter and there is an option for IS NOT NULL. That should…

As of right now you'll have to edit the name in the ETL process. However I do believe they are working on a way to edit the name/column type at the schema edit screen for the dataset. Might be something we see revealed in a couple months at Domopalooza. Hope that helps, Valiant **Please mark "Accept as Solution" if this…

Take a look a the General section under Chart Propertes. I'm not sure which chart you're using specifically but there is normally and option to change the # of seres on the left scale (# of lines vs bars). See if one of those is what you're looking for. Sincerely, Valiant **Please mark "Accept as Solution" if this post…

I'm going to guess the issue has to do with your date column. If distribution date is seen as a date field and not text, you need to update your conditions to look like this: SELECT *, CASE WHEN `account_number` = 20160001 and `document_number` = 57290 and `distribution_date` = '2018-12-29' then 'exclude' WHEN…

What option do you have set in the Append widget?

Currently different drill paths depending on what is clicked are not available. The only way around this would be trying to do something similar to the Page Analyzer Links I mentioned on your other post. This would make for a good idea if one doesn't already exist for this…

What you're looking for is referred to as a Page Analyzer Link (https://knowledge.domo.com/Visualize/Adding_Cards_to_Domo/KPI_Cards/Transforming_Data_Using_Beast_Mode/Sample_Beast_Mode_Calculations%3A_Miscellaneous_Transforms#Creating_Page_Analyzer_Links_(or_Deep_Linking_with_Filters)) This will allow you to basically pass…

Got it! Took a bit of thinking but here you go. I took the example dataset you gave me as the "Entry" and was able to do it with the following steps: Here's the details for each step: Always interesting trying to do things like this in ETL. Best of luck! Valiant **Please mark "Accept as Solution" if this post solves your…

Can you provide an example of the dataset in Domo? Will make coding the final result easier if I know what you're data looks like inside Domo. And you're definitely on the right path. As far as if it's possible, yes it is. What you're going to need to do is basically create the card as you want it in a dataflow (doing the…

The way you would need to do that is to break the lines up in the previous and future values. So based on your example, instead of using 1 measure and a category to split the line into the blue and orange lines. You would instead create 4 beast modes, 2 for your previous (actuals) and 2 for the future values. Example…

Here's the basics on how I would write this as a beast mode: CASE WHEN `Date` >= DATE_SUB(CURRENT_DATE(), INTERVAL 3 WEEK) AND `Date` <= DATE_SUB(CURRENT_DATE(), INTERVAL 2 WEEK) THEN `Actuals` END Hope that helps, Valiant **Please mark "Accept as Solution" if this post solves your problem **Say "Thanks" by clicking the…

Could you use a filter to grab the records that are incorrect and filter them out? The use of filters is the only way I would know to remove items from a dataset. You would end up with a new output, but that new output could then be used as your new base dataset. Hope that was of some help, Valiant

You would need to create a Beast Mode basically says: SUM(CASE WHEN `Category` like 'Expired' THEN `Value` END) / SUM(`Value`) Then select that Beast Mode as your summary number. (one tip on summary numbers, they will only allow you to use a beast mode if the beast mode is an aggregation. Can't put something like 1+1 would…

So a bit cleaner version of the Status calculation would look like this: CASE WHEN `Delivery` = 'Done' THEN 'Complete' WHEN IFNULL(`Quantity`, 0) < IFNULL(`Order Quantity`,0) THEN 'Pending' ELSE 'Complete' END No need to nest the case statement here. And actually you could make it like this as well: CASE WHEN…

https://knowledge.domo.com/ is going to be what you're looking for. You can search for pretty much anything in Domo and find guides on how to do pretty much anything as well. The second option if you can't find something on that site is to ask here. The Dojo is a great resource for having your more difficult questions…

So this is a shot in the dark, but it might just work. Take a look at this article on Page Analyzer Links: https://knowledge.domo.com/Visualize/Adding_Cards_to_Domo/KPI_Cards/Transforming_Data_Using_Beast_Mode/04Sample_Beast_Mode_Calculations#Page_Analyzer_Links_(or_Deep_Linking_with_Filters) We have a few of these set up…

If you've converted the list into multiple columns, you should be able to then take that table of columns into the ETL section and use the Collapse Columns widget. This allows you to specify a column that will 'hold the column labels' and another to hold the values. If you have no values, you can just use a placeholder.…

In order for a page level filter to be able to filter across all of your cards, the name of the column you're using to filter will need to be the same across all the data sources in play. You'll also need shared values among that column on each dataset. Once you have that, you should be able to use a page filter and have…

This almost sounds like a join. Simple syntax for something like that would be: SELECT FROM Dataset AS p LEFT JOIN (SELECT * FROM Dataset WHERE type = task) AS t ON t.task_parent = p.project LEFT JOIN (SELECT * FROM Dataset WHERE type = subtask) AS s ON s.subtask_parent = t.task_parent WHERE p.`type` = 'parent' If…

Our main install of workbench is on a shared server. The drawback of installing on workstation being that if it's ever turned off then scheduled jobs won't update. We haven't experienced any issues with data upload in that setup (save the occassional database issue). Hope that helps, Valiant

So it sounds like something is getting crossed up using Mon-Sun as your week range. With that being the case, I'd look to apply a calculation to my dataset to determine the week number myself. And hard code the 52 week over week comparison. You could set it up like this: (Week() function…

You would need to use an IP to location database mapping like this one (https://lite.ip2location.com/) in order to get either the LAT/LONG or the ZIP. Once you've joined your IPs to this you should be able to mape them. Hope that helps, Valiant **Please mark "Accept as Solution" if this post solves your problem **Say…

So I can only speak for what I've experienced in our environment and maybe this is more of what you're looking for: * Pages: The only times we've seen performance issues with pages is once we have a large number of cards (ie, 30-40) and many of those cards are expanded to be larger on the page. There can be some delay in…

While you can sign up for test environments through the developer site on Domo, you can't publish those items to a production instance. It's often easier to create a new page without sharing it out and develop there until you're ready to share. The other option is to copy an existing page, (duplicating all of the cards).…

If you're trying to have millions or rows processed at the card/dashboard level, I would suggest attempting to summarize the data via an ETL or SQL transform and then build your cards on that instead. Example: Instead of using beast modes to sum values in your card, do the sums via the ETL, grouping the categories they way…

So you can calculate the average daily amount by doing something like this: `Value` / DAY(LAST_DAY(`Month`)) That will convert each month value to the last day of said month and then strip the day value from it. So it would be 100000/31 for January and 121002/28 for February etc.. Hope this helps, let me know if you have…