GrantSmith Coach

@Jbrorby - Thanks for following up and your contribution to the Dojo community!

@User_32612 I'm assuming you're using a beast mode for your x-axis - do you have any fields listed in your sorting? That may throw off your grouping. You may want to come up with a similar beast mode to define your sorting such that anything pre week 16 would be a value of 15 so that they'd sort and group based on the same…

Thanks for the information @jaeW_at_Onyx I'll have to play around more with the syncing in custom apps.

Correct you can only write to an existing dataset in AppDB not in Domo proper

Hi @the_tree What specific issues are you running into? What are the error messages you're getting? Are you trying to write to a new dataset? Has the dataset been correctly defined in your manifest file?

Hi @Daneia , I believe this is because, looking at the connector FAQ tab, it's using version 5.0 of the Instagram API which has been retired. They're on v11.0 now. You could try and reach out to your CSM or support and see if they would get that API connector updated.

Hi @kacy How are you ingesting this data? Are you attempting to do an UPSERT? What it boils down to is that the column you're using to identify a row's uniqueness isn't unique. You'd need to reimport your data such that you don't have duplicate IDs if your keys are set to the column that denotes uniqueness. Alternatively…

Hi @jbandley @MarkSnodgrass offer's a good solution. I was going to suggest another option utilizing SUBSTRING, INSTR and LENGTH but his is a simpler option.

Hi @user069636 Whenever I typically need to do some period over period comparisons I actually restructure my data so that I have a report date and a "comparison date" (the actual date the metric was recorded on) and calculate it as necessary. This allows you to have custom defined periods (like 2 weeks ago and a week ago).…

Hi @nbrx Whenever I typically need to do some period over period comparisons I actually restructure my data so that I have a report date and a "comparison date" (the actual date the metric was recorded on) and calculate it as necessary. This allows you to have custom defined periods (like 2 weeks ago and a week ago). You'd…

@Shumilex How is it not working correctly? What values are you getting for hours <1, 1, 2, 3? Which calculation are you utilizing?

Those are actual tiles within the Magic ETL platform. You can use those in your Magic ETL to convert your string to a date.

In that case if Domo is unable to convert the string directly to a date you may need to convert it to a timestamp first before you then convert it to a date.

Hi @user048760 Was this field imported as a timestamp or is it configured as a string? You can utilize the Set Column Type tile in Magic ETL 1.0 or the Alter Columns in Magic ETL 2.0 to force the data type to be a Date.

@emmanuel_fabre Is your average higher or lower than the Excel value? With your 4-line example would your average be 78678.0625? When using AVG it excludes NULL values from its calculation. If your Beast mode value is higher than the excel value it may be because it's excluding those. Should the conversion rate be 0 if…

Hi @emmanuel_fabre How does the data not line up? Are you calculating an average of the averages or an average of the entire dataset in Excel? Simply put do you want: AVG(Total Views / Total Conversions) OR SUM(Total Views) / SUM(Total Conversions)?

You can also delete accounts from that same menu which you may want to do unless you actually do have 12 different accounts to connect with. Also, @MarkSnodgrass - I'll beat you next time! :-D

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.