jaeW_at_Onyx Coach

@jmcgurl , why are you hard coding all these filters into your beast modes? would it not make sense to use Quick Filters or Filter Cards to pass Region filter context to your viz? (this allows you to avoid single use beast modes. @GrantSmith good beast mode but careful -- this won't work ... `REGION CODE`= 'NA' AND `REGION…

What's the requirement? you described technical solutions. but why do you need what you're asking for? if you use HTML tags to control images sizes in a table card, yes you can pass styling in the HTML. Domo has limited support for that in table cards. I don't believe that's possibe in image cards. You can upload files to…

typically Domo can't show data in analyzer if it doesn't exist (i.e. if there is no data for last week it can't just make stuff up.) What is the 'right' baseline? In this videoe, https://www.youtube.com/watch?v=Xb4QgKYgaqg&t=261s, I describe it as defining the 'universe of options'. In your case, it sounds like you need a…

emm.... not entirely accurate @GrantSmith 1) Domo stores app related data in AppDB which is a NoSQL database (so operates on collections of documents, similar to MongoDB) 2) you CAN sync an AppDB to Domo's Vault as a dataset (see link below), it does create and update (via UPSERT) a dataset in Domo.…

Sorry, I don't.

handful of questions. why 16 to 28? is that b'c you're specifically interested in that point of time or is the timeframe dependent on today()'s date? (in which case build your filters and axis on a variant of the current_date() function. if it were me I would build an offset date dimension table so I can use other chart…

https://youtu.be/hRwrZABP8RE?t=107 Daren and Ken talk about it a little in this video.

@Afolabi that data does not exist in a dataset. You could sniff network traffic to uncover Domo's APIs and then create a dataset using tools outside of Domo like Powershell or Python.

Post a sample dataset. I'm not convinced the data is actually shaped the way you described, otherwise you should get a result.

what is the insights portal? 3) why would you recreate it? the overview page is unique to each user. it seems ... counterintuitive to create a dashboard that only you have access to. typically people only copy a handful of cards that are uniquely important to them to their overview page.

if the numerator and denominator are not in the same row then yeah... you can't / shouldn't use that column (description). Because each log in hasn't been attributed to a description.

if Total is an average. And then you want to take the average of Total, then you're trying to take the average of an average. on most days of the week that's considered mathematically problematic. if that's your requirement though avg( colA/colB ) should yield the correct result; however IF the values for ColA and ColB are…

In your screenshot you've applied the filter for yesterday. (top right corner) if your data is limited to yesterday then you cannot include / consider the data from one year ago. so when you divide by null you get null.

it's all in their documentation... check with support and confirm that the documentation is not out of date. also confirm that your objects are arrays when they arrive...

@Fatias true, i believe you would have to have the direct sign on exception enabled to use this method.

just google it! https://developer.domo.com/docs/domo-actions/start your CSM should be able to get you additional information via support but it, addmitedly, is not the easiest to find resource. if it were me, i would try to find another solution than domo-actions.

In general it sounds like you're struggling with 3 major issues SUM(`Total A`) / NULLIF(SUM(`Total B`),0) 1, don't convert your denominator to null if it's 0. you can't divide by NULL. that's bad math. 2, understand that this math is taking the sum of the entire column and dividing by the sum of Total B. In your…

use a table card. separate your numerator and denominatorr into separate beast modes, then add the columns to your axis. I'm betting you don't have Description in the rows that constitute the Denominator, which drives your denominator to 0 and N/0 is undefined, which domo would represent as a null or blank.

Have you confirmed that the domo library is available? can you accomplish other actions like get data from Domo? it seems unlikely that they would have deprecated onFiltersUpdate b/c that's integrated into all sorts of apps. Given t.map isn't a function, have you also confirmed that t is an array when your code executes?

can you use libraries that just run in the front end? Domo does have "Domo Actions" which theoretically was developed to use the Domo Accounts objects in apps to support saving and storing credentials.

agree with @GrantSmith , the solution to this problem should be implemented in the structure of the data instead of logic in a beast mode. this is probably the kind of thing that you need to be universally true not only true in the card that happens to be using the correct beast mode. "single version of the truth" and all…

export const get_authToken_domo = async (EMAIL, PASSWORD, DOMO_INSTANCE) => { const auth_url = `https://${DOMO_INSTANCE}.domo.com/api/content/v2/authentication`; const body = { method: 'password', emailAddress: EMAIL, password: PASSWORD, }; let resp = await fetch(auth_url, { method: 'POST',…

what you can do is create a webform (or a dataset generated via ETL if you're using the today() function) with the columns JOIN_Col = 1 and then the date you want to filter on. JOIN it to your transactional dataset using a Dataset View where on the transactional dataset you also have a JOIN_COL =1 Now when you change the…

... you're consistently making the same decision to nest COUNT DISTINCT inside CASE statements. Be very careful, this is a bad habit to get into and can yield unexpected results. I suspect you have a data interpretation problem. quick question. you're doing count distinct of report date and agent ... but is your count…

In most of my consulting engagements, a hybrid of @MarkSnodgrass and @ST_-Superman-_ 's approach works best. Scott is describing the output of Enterprise Stacker, a tool built by Domo that UNIONs all the data and the aggregates it down to a Value's column as in Scott's screenshot. Very clean, but when you pre-aggregate…

1) be careful of nesting aggregations, avg, inside the CASE statement. You can't apply the CASE statement. You usually won't get the desired result. 2) you cannot GROUP BY the result of an Aggregation (CASE ... AVG ... ) Case When HOUR(SEC_TO_TIME(AVG(TIME_TO_SEC(TIMEDIFF(`closedDate`,`createdDate`))))) <= '1' then '1'…

is it fair to assume that you've imported the domo.js library?

@StefanoG your custom app cannot require a backend server / backend functions. It must all 'run in Domo'. You could try sending requests to serverless functions hosted in Azure or similar.

I don't think Period over Period is the right chart type for you. it sounds like you want to know "how many machines syncced last month" and "how many machines synced this month" I don't think you can accurately answer both of those questions with the data provided. // EDIT: I would not structure my data this way. If it…

@StefanoG what's the problem you're encountering? Domo does take all data and stores it in UTC. Are you running into an error? Are you getting unexpected results? https://domohelp.domo.com/hc/en-us/articles/360043439073-Time-Zone-Troubleshooting-FAQ