GrantSmith Coach

This video may provide some insight as to why there's a double aggregation: https://youtu.be/gO8OLpsAk4M?t=1066 Simply put Domo aggregates the data twice if you have another grouping on the card so you need a double aggregate.

Because of how Domo functions there isn’t a way to filter multiple fields based on a single value like you’re wanting to do via a parameter

Have you tried the AVG function? It ignores NULLs AVG(Score)

Hi @Fatias If you're trying to connect to your_instance.domo.com you'd need an authenticated API key and pass that into the 'X-DOMO-Developer-Token' header. This is how you can authenticate with your instance APIs and not the api.domo.com APIs. You can generate a token under Admin -> Authentication -> Access Tokens. This…

Hi @User_32612 You could utilize a window function for your denominator (may need to talk with your CSM to turn this on in your instance): SUM(SUM(case when `Week` = 42 then case when `Year` = 2020 then `Dollars Total` else 0 end else 0 end)) OVER () However if Prime Day ever shift again in the future (it will) you have to…

@RBGatTGTandBE I'm still able to put multiple metrics under the series and they plot the individual values using a line graph. Are your metrics actually green (metrics) or is it blue (dimension)? Which card type are you using?

Hi @Shumilex When dealing with datetimes I prefer to utilize the UNIX_TIMESTAMP function to get the number of seconds since 1970-01-01 12:00:00 AM and then doing some math to get the difference in hours. -- Calculates the difference in seconds between both timestamps -- UNIX_TIMESTAMP gets the number of seconds elapsed…

Hi @Shumilex Have you tried starting with a table card and making sure your data is being populated correctly? Are you getting values 1-24+ for your series? What are you using for your value?

Hi @Jbrorby You may be able to get around it by utilizing a MIN or MAX function on your appointments and possibly might need a window function. MIN(MIN(`Logged in hours per day`)) OVER (PARTITION BY `Staff` , `Login Date`) / MIN(MIN(`Logged in hours per day`)) OVER (PARTITION BY `Staff` , `Login Date`)

Hi @MichaelClark I don't believe the JSON connector supports pagination. You'd need to write your own custom connector to allow you to page through your results.

Have you tried breaking down your case statement into multiple beast modes to help diagnose which portion of your beast mode is having issues? Also just looking at your code you need the question mark to be surrounded by quotes: (CASE WHEN (COUNT(DISTINCT `ReportDate`)) >= 1 and (COUNT(DISTINCT `Agents`)) >= 1 THEN '1'…

@sides I'd recommend offering up that product feedback to Domo. If it's really annoying you, you could try utilizing Magic ETL 2.0 instead. You'll get an efficiency increase as a bonus.

Hi @sides You'll want to reach out to Domo Support as this is an issue on their end and they'd have more insight into your issue.

@sides - Have you moved any tile or opened the settings on one of your tiles? Doing those will typically cause Domo to think something changed.

Those are the current options we have. You may be able to hack around it by calculating your buckets manually and then using color rules to automatically color those buckets. Not ideal. I’d recommend adding this as an idea in the idea exchange on the dojo.

You’re correct that it’ll return the same number from what I’ve seen in the past. If you want it more randomized for each row you’d need to run the random function within an ETL

You can create a beast mode in analyzer. On the bottom right there should be a button that says Add calculated field. It will also give you the option to save the beast mode to your dataset which will make that same calculation available for other cards you make with the same data set

Hi @jblecha You can utilize a beast mode conditionally set the value and use that as your series. CASE WHEN `field` = {"MODE":"Auto","Rule":"Tree"} THEN 'Point - Tree - Batch' WHEN `field` = ... ... END Alternatively you could parse your field values in an ETL or you could have a separate dataset with two columns, one for…

Hi @user10110 Domo doesn't have anything built in to calculate a normal distribution probability. You'd need to calculate it yourself via an algorithm

Hi @MysteriousDomo Currently this is not something we can change the user end. You might try talking to your CSM and see if Domo is able to change the format on the backend but very likely it will be an additional cost for the customization if it is indeed possible.

Hi @Alex_us This video may help explain the APIs and how they interact with Domo. It's a very technical aspect having to interface with Domo in this specific way and typically need to utilize some programming language to build a pipeline.…

Hi @user046467 I’ve run into this issue in the past. For me I had to tell it to import a single day, run it and then import the range I want

Hi @eriena Have you tried a different browser or closing your current one and reopening it?

Just a note you can utilize the regular expression I gave in an ETL using the replace text tile. You just need to make sure you select Use Regex from the gear menu on the search text field (middle one) Also for clarification [67] says any single character in the list to match to

Hi @hilsmith What does your regex look like? you can try something like this ’’’ regexp_replace(`subject`, ‘^.*(87[67]\d{4}).*$’,’\1’) ’’’ I’m on mobile so sorry for the bad formatting

Hi @dacorson How is your window function written? If your card has another field you're grouping by then the window function won't get interpreted correctly. You need to wrap your window function aggregate in another aggregate. for example: SUM(SUM(1)) OVER () I've documented this in another post of mine here:…

@nshively Can you calculate the CTR by taking the clicks / impressions?

Hi @kboudrie You can utilize case statements and window functions (you'll need to talk with your CSM to turn on windowing functions) SUM(SUM(`col_1`)) OVER (PARTITION BY YEAR(`Date` - INTERVAL '5' MONTH) ORDER BY (`Date` - INTERVAL '5' MONTH) / SUM(SUM(`col_2`)) OVER (PARTITION BY YEAR(`Date` - INTERVAL '5' MONTH) ORDER BY…

Hi @Alex_us There's likely a "lowercase p" public API endpoint to get a list of all of the embedded cards their their URLs to then parse our the ID. You'd just need to inspect your Domo Everywhere page list to determine which API endpoint it's utilizing. Note that as this is what Domo calls "lowercase p" public it's not…

An alternative is to utilize a Python script to use the pydomo package and export data from Domo and then utilize the package from Amazon to upload your data to Redshift (https://aws.amazon.com/blogs/big-data/using-the-amazon-redshift-data-api-to-interact-with-amazon-redshift-clusters/). This would be a free method of…