Best Of

Re: January Virtual User Group Kickoff

As it turns out, it WAS amazing! Thank you to the team that pulled off this excellent event for the community.

JasonAltenburg

2

Re: A more flexible way to do Period over Period comparisons

Dataset Format Overview

The resulting dataset will have three different columns:

Report Date - This is the date you will use in your charts / graphs
Comparison Date - This is the date you will join your dataset to
Period Type - This defines the type of the period / offset

GrantSmith

2

How to clean up clutter - User Conference Jan 2022 notes

If you would like to replicate the dataflow showed in the presentation, go here - https://doc.clickup.com/d/h/8895x-1107/6de82f6ad073c84/8895x-147

You can copy the code at the bottom of the page, open up a new Magic ETL 2.0 canvas in Domo and use the keyboard shortcut for “paste” (command + v on a Mac) to get the flow onto your MagicETL canvas. You may need to scroll down to see it on your canvas.

If you’re interested in learning more about the MajorDomo Deputy, which can leverage this type of dataset to manage your Domo environment at scale, feel free to reach out to us at interest@crystalballers.ai

john_stevens

7

Re: Mandatory Single Select Filter

If you click the gear icon on any of your quick filter fields in Analyzer, you can change it from Multi select to Single select.

MichelleH

2

Re: Rolling 12 Month Avg

How far back does your data go? If you don't have any data prior to 2020-Q4 it'll return NULL because there are no prior rows for it to pull from. When you have a NULL with a simple arithmetic operator (=, -, *, /) the entire result ends up being NULL. You can wrap your entire LAG...OVER() in a COALESCE function and coalesce it with 0 to force NULLs to be 0

COALESCE(lag(count(... over (order by `Quarter`), 0)

GrantSmith

2

Re: Rolling 12 Month Avg

Hi @DomoNewbie

Have you read my prior article on rolling averages using window functions? This may help you out: https://dojo.domo.com/discussion/52679/domo-ideas-conference-beast-modes-rolling-averages#latest

GrantSmith

1

Re: Using WorkBench to Connect Azure AD to DOMO?

Hi @JoeR_PSIT

It doesn't appear there's currently an Azure AD connector that's been written. There is an API that Azure AD offers for some reporting on sign-ins and audit logs which is outlined on Microsoft's website: https://docs.microsoft.com/en-us/azure/active-directory/reports-monitoring/concept-reporting-api

You have a few options to get this information into your environment however it will require some technical expertise. You can attempt to write you own custom connector (https://developer.domo.com/docs/custom-connectors/connector-dev-studio) or you can utilize python and write your own script to pull the data and then ingest it into your instance using the pydomo package (https://github.com/domoinc/domo-python-sdk)

GrantSmith

2

Re: Checkbox Selector not showing all values?

If you don't have anything in the optional group by field, I would put the same field that you have in the items field into the optional group by and choose count as the aggregation type. I would also check the date range filter if your dataset has a date field and see which field it is using for the date range. If your dataset has multiple date fields, Domo may be choosing a date field that is incomplete, causing not all fields to display.

If neither of those fix the problem, selecting Reset Chart Properties can help as well. Also, I'm assuming there is nothing in the filter properties that would exclude one of your items.

MarkSnodgrass

5

Re: Beast mode that would put people in a specific group based upon a date

Yes, you could do this a couple different ways, depending on how you want to look at your formula. I might go with this:

CASE WHEN DATEDIFF(CURRENT_DATE(),`dt`) >= 90 THEN '90 days late'
WHEN DATEDIFF(CURRENT_DATE(),`dt`) >= 60 THEN '60 days late'
WHEN DATEDIFF(CURRENT_DATE(),`dt`) >= 30 THEN '30 days late'
WHEN DATEDIFF(`dt`,CURRENT_DATE()) >= 90 THEN '90 days future'
WHEN DATEDIFF(`dt`,CURRENT_DATE()) >= 60 THEN '60 days future'
WHEN DATEDIFF(`dt`,CURRENT_DATE()) >= 30 THEN '30 days future'
ELSE 'Not Late'
END

Notice in the new 3 statements that I added, I switched which fields is the first parameter and which is the second. This will allow you to look at future dates and it would return a positive number when evaluating.

You might want to test by just creating a beast mode that only has the datediff function in it and view the results in a table card. Once you see the results of that, it will make it easier to properly build out your case statement.

MarkSnodgrass

1

Re: Beast mode that would put people in a specific group based upon a date

I would create a beast mode that divides them into groups like this:

CASE WHEN DATEDIFF(CURRENT_DATE(),`dt`) >= 90 THEN '90 days late'
WHEN DATEDIFF(CURRENT_DATE(),`dt`) >= 60 THEN '60 days late'
WHEN DATEDIFF(CURRENT_DATE(),`dt`) >= 30 THEN '30 days late'
ELSE 'Not Late'
END

Replace 'dt' with the name of your auction date field.

You can then add this field to a pivot table and also to your filters to filter out the not late group if you don't want them to show.

MarkSnodgrass

1