GrantSmith Coach

This sounds like a bug. I'd recommend opening a support ticket with Domo to have their engineering team take a look at for you.

You could pre-filter your dataset using two dataset views (period type = current and period type = last year) and then use those as an input into your ETL. That'll do the filtering in the adrenaline layer (essentially in memory) instead of having to transfer all 80M rows you have over the to ETL process and transferring…

You can use a case statement to conditionally return a value or NULL if it doesn't match the logical expression. Something like: CASE WHEN LAST_DAY(`Period Date`) <= LAST_DAY(CURDATE()) THEN `Value` END You can then use this beast mode in place of your original value. I'm using LAST_DAY to return the last day of the month…

Since you're using the PoP dimension you can create a new ETL with the PoP dataset as the input, have two filters `Period Type` = 'Current' and `Period Type` = 'Last Year' then do a join of these two fiilters based on the report date. That will combine them together on the same row for your output dataset.

I’d recommend looking into the DomoStats connector to pull metadata information about cards pages or datasets among other options from your instance to then visualize or alert on.

How are you attempting to clean these codes? What is the business logic you’re needing to replicate?

Are you using Date Query parameters? I'm assuming that's the case in which it would cause Domo to validate the date string. In this instance it won't work if you're using relative values. Have you tried passing it via a string query parameter?

Since it's not supported in Domo's connector you'd likely need to write your own connection to it. Currently there's two options you can pursue to make your own interaction with the Asana APIs: Write your own custom connector: https://developer.domo.com/docs/custom-connectors/connector-dev-studio (JavaScript) Utilize…

Since there's no built in connector for Ironclad to Domo you'll need to create one yourself. You have a few options, all being technical. Write your own custom connector: https://developer.domo.com/docs/custom-connectors/connector-dev-studio (JavaScript) Utilize Python to write your own script to interface with the API and…

You can filter your card to display only the latest information using analyzer and then on you can edit the dashboard it's on and change the interactions and tell it to not be affected by any filters.

Segments only creates a subset of your data but doesn't remove it from the original dataset. If you need to you can create two beast modes to do the Canada filtering for each of your metrics -- Canada CASE WHEN `Country` = 'Canada' THEN `Value` END -- All Others CASE WHEN `Country` <> 'Canada' THEN `Value` END

You'll need to log a support ticket and have Domo's connector team update the API endpoint it's calling.

@Sudershan - Glad you got it figured out. Make sure to mark your answer as a solution so others will be more easily find it if they have a similar issue.

@MattBeal If you're not pre-filtering or dropping columns from your dataset with your views then you're likely not to see any improvement as the same amount of data needs to be transferred over to the ETL processing platform.

Data Fusion (or Blend as it's sometimes referenced) is the preceding version of DataSet Views. My understanding is they have the same functionality underneath but views offers more functionality.

In an effort to more simplify the comma delimited version of the beast mode I'm posting an alternative version instead of having to check every single different potential lengths it will automatically calculate the different sections automatically making the beast mode more readable. This version also handles numbers up to…

Hi @jmmc When I'm doing ETL optimization I typically like to think about being a teapot - Short and Stout. Short - Filter / Drop unused columns / reduce the amount of data as early as possible. Another option may be to create a DataSet view of your datasets if you're filtering the data / dropping columns first, this will…

Use Year To Date as the option instead. Alternatively you can reformat your data and use a custom date dimension offset to better handle period over period analysis. I’ve done a write up on this here: https://dojo.domo.com/main/discussion/53481/a-more-flexible-way-to-do-period-over-period-comparisons#latest

@justin-millheim do you have any insight into this?

.

You can use a table card and sort on the number of responses ands then in the analyzer settings under filter you can set the number of rows to return to 3. Doing a drill path to get all of the reasons will be difficult as Domo automatically filters your drill card based on what was selected

Some minor tweaks to your beast mode: CASE WHEN YEAR(`Booking Year Nbr`)= YEAR(CURDATE()) THEN "CY" ELSE "PY" END

The Java CLI has a swap-owner command with the -r flag to swap the owner of a report. Does require admin privileges to perform the swap.

This is something done with your IdP / Identity Provider using Single Sign on. You can read more on it here: https://domohelp.domo.com/hc/en-us/articles/360043428233-Domo-Mobile-Security

A calendar dataset is one that lists all of the dates as sort of a dimension table. The sum is the count of dates you're getting from the group by when grouping on your ID field. You just need to join your dataset with the group by tile output based on the ID field to tie the sum of days / count back to your original…

@MichelleH - Good catch, thanks!

@NathanDorsch It's the correct syntax. Sometimes the syntax highlighting has a few issues highlighting everything correctly depending on the keywords.

Currently no, only the user can modify their own notification settings. That'd likely be a good idea to submit to the idea exchange to give admins more control of notifications.

CASE WHEN COALESCE(TRIM(`field`), '') = '' THEN 'Blank' ELSE 'Not Blank' END COALESCE will return the first non-null value it finds, used in this case it's saying if the field is null return an empty string. I've wrapped the field in a trim to remove any leading or trailing whitespaces in case someone has a value of all…

You can use a beast mode with CONCAT to join multiple column values together. CONCAT(SUM(`delivers`), ' delivers ', SUM(`delivers`)/SUM(`total`), '% delivery rate')