jaeW_at_Onyx Coach

can you just APPEND the dataset as you load it into Domo? Maybe add the current_date() as part of the ingestion process? Looooooong term it'll be faster than recursive dataflows but if i'm honest for a 5k row dataset, recursive will work fine. It just comes with risks if you ever accidentally blow up your data, because…

While @GrantSmith 's assessment that you lack an ELSE clause is not untrue, I don't believe it'll get you to the heart of the problem. SHORT ANSWER. Restructure your data or you'll probably get the wrong result. LONG ANSWER Yes ... you could aggregate the data and get a result. SUM(CASE WHEN 'ConversionTypeName 2` = 'Sale…

You can interact with the undocumented APIs via the Domo CLI, https://knowledge.domo.com/Administer/Other_Administrative_Tools/Command_Line_Interface_(CLI)_Tool, insofar as ... you can do more advanced scripting. The APIs on developer.domo.com Domo support are contractually obligated to ... support ... so Domo minimizes…

add current_date() as a column in your google sheet, then set up your connector to do an APPEND instead of a REPLACE. (it's under the scheduling tab). ... or do a recursive dataflow if you must ? More information about recursive dataflows than you ever wanted to know: https://www.youtube.com/watch?v=JNQFZCj8JcQ

"Depending on how granular you'd like the snapshots and the number of employee records this could end up being a lot of records. What I'd recommend is having a dataflow run every so often (probably monthly unless you need it more granular) where it could calculate the number of employees, hires, terminations and status." I…

it depends on the API. if you're using any of the APIs identified on developer.domo.com, you're Access Token or ClientID and Secret automatically direct you to 'your instance of domo.' the only reason you'd use a different URL is if you were using non-public APIs (APIs not listed under developer.domo.com)

Not to flog a dead horse, but the issue with years or months starting in the middle of weeks is literally the issue that dimension tables were designed to address. If you build it once, you can eliminate all these dense and convoluted CASE statements. This is a recurring issue in the Dojo, so I built a tutorial video on…

If i had to guess you have an incredibly large dataset. What if you just write a FOR LOOP and then stitch the data together in Python ( i assume you're using Python). keep in mind, your dataset has to fit in memory. it maybe beneficial to write your data to csv between each iteration of the for loop. also, executing…

Did a tutorial on this topic on my YouTube channel. Good luck. https://www.youtube.com/watch?v=PVbOeLSae9o

your main axis is client, it's confusing what you expect it to look like given that I assume one company could be distributed across multiple clients. anyway, try sum(sum(amount)) over (partition by company). you may need to ask your csm to enable the 'add window functions to beast modes' feature switch. 

@Crisocir be super careful with the aggregate functions particularly MAX() and COUNT(DISTINCT) OVER ... they will work for ONE card with an axis but as soon as you change the axis it'll probably yield the wrong result. So, while you may get the 'right number' when you look at MAX(MAX()) by Department and Year, if you…

https://www.youtube.com/watch?v=39VHAQEYHAc&feature=youtu.be when the video finishes uploading, here's how you can accomplish your requirement using dataset views. in the absence of DSVs, you can aggregate your data using Magic or any other ETL tool. 

https://knowledge.domo.com/Administer/Specifying_Company_Settings/033Time_Zone_Issues_FAQ please review this document! it sounds like Domo is behaving as designed. if it's not, can you pls provide a screenshot of the raw datatime column and a screenshot of what you're seeing in cards? Domo should adjust the data to the…

are you able to successfully filter on Date is IN ? (i.e. do you have the syntax for specifying a date correct?)

Magic will work in a pinch. Dataset Views will work as well. you can even construct your CASE statement within the DSV. NOTE. You CAN implement a window function inside the DSV, but be advised it can have some ... unexpected interactions in cards, ALSO the rules of what you can and cannot do in a card extend to the rules…

So ... while window functions are amazing for many things, it won't work when you're trying to do a count distinct. why? SUM( COUNT(DISTINCT CASE WHEN `Year`= YEAR(CURRENT_DATE()) AND `Month #` <=`Month # for Today` THEN `Customer Name` END )) OVER () keep in mind what is happening under the hood. first Domo does a…

re issue 1: use a LEFT JOIN to keep all rows from the LEFT side. then as you said, add an isMatch flag = 1 or 0 based on if it matched on the right. You could output them all to one dataset and then use a Dataset View (also a beta) to subset the data by 'with matches' vs. 'all data'. re:issue2: instead of doing a GROUP BY…

i don't know the answer. maybe try sitting with a sharepoint admin who can temporarily provide credentials ... then you can verify 100% that it's a credentials problem and not an ... IP Whitelisting or any other type of problem... once you've got a connection with an admin account, delete those credentials from Domo and…

ok, so if i understand you correctly, every month you take a snapshot of the employee table. and then you also have a flag that says 'most recent record' or something like this that gives the current state of the employee. and you want to navigate from the 'most recent record' to a previous month. what you could do is have…

i'm reading very quickly, but i'm pretty confident it won't work as set up. MY ASSUMPTION OF YOUR HIGH LEVEL GOAL A list of availabilities and the number of employees who have that xyz total availability given a certain time frame. <8, 5 <15, 23 <21, 100 >=21, 14 If that's your goal, you can't get it using window functions…

https://www.youtube.com/watch?list=PLUy_qbtzH0S4CkHBUvpOVpLNJluk6upOn&v=wmMrnPO9ivY in this tutorial i'm building an AR aging report, but the concept is still the same, just build a card where you can define the point in time you want to use for your YTD value. What's cool about this is that if you had two rows in your…

while @GrantSmith 's statement that you can't divide by 0 is true, that's not the root cause of your problem. (i suspect). you can't write this. even if you ignore the divide by 0 issue, it's still logically wrong because your beast mode will only ever return either 0 or NULL. Because after aggregation has been applied,…

as @GrantSmith when you apply filters it sets the context for what data is available as you calculate the denominator in the percent of total calculation. there is a new beta feature in development that will allow one visualization to support 'filter groups'. the title of the feature may have changed, but the gist of the…

Just JOIN the CLIENT_ID and the CLIENT_LegibleText to your dataset ... then build a filter using CLIENT_LegibleText. Am i not understanding something?

you really should consider implementing a date dimension that contains one row for every day since the dawn of time and calculates your fiscal calendar weeks etc. to assist you could create a webform that indicates the start of each fiscal year and then just use SQL to derive the rest. The risk of embedding it in beast…

... i don't know your data, but i'm not sure why you'd do it in a GROUP BY instead of a FORMULA tile. Also, instead of managing crazy math with a CASE statement, create an Interval column that says how many months to go back (i.e. 1 or 2) and then use your Formula (or GROUP BY) tile to pass the interval (number of months)…

InStr and CHARINDEX are common SQL functions that can get the job done. you can use Regex expressions in Magic (Replace Text)

@user32470 , i'll tell you what i tell everyone. ANYTHING (almost ? is possible in Domo if your data is structured the right way. For this use case, it'd help us if we had a sample of your data and a mockup of your screenshot. Given what i understand about your data, assuming you haven't gone out of your way to restructure…

yes the problem is as you described. but also ... avoid making one dashboard for each region or group of hospitals. you're going to create a nightmare where you have to manipulate 10 dashboards just because everyone wanted one change... instead use a filter card to define the hospital groups if some hospital groups have…

send a ticket to support@domo.com