Best Of
Re: Page Level Date Filter nulling when not available in every dataset
@crico Since you are using multiple datasets, I recommend using dynamic date range filters and Filter Views. The global date filter is not tied to a specific date field, but instead uses whatever field is used in the Date Range settings of each card.
Re: How to fix 'Cannot Save' error in Scheduling?
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.
Re: Struggling with Beastmode formula
@NathanDorsch You don't need your final "end". You only need an end when you're dealing with individual CASE WHEN statements.
Re: Struggling with Beastmode formula
Hi @NathanDorsch try removing the last "end" and see if that resolves the error.
Re: Show the latest data without affecting date card filter
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.
Re: Pull a list of all datasets in Domo?
@DataLawton For finding datasets that are no longer used, you can also click on Data in the toolbar at the top and then go to the Datasets section. From there you can use filters to find datasets that don't have any cards and flows.
Re: Pull a list of all datasets in Domo?
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.
Re: Data Cleaning
When you have multiple items to clean, you will have one case statement and multiple when statements, like this:
case when Right(`Entry Store`,5) = 'PTO"}' then 'PTO' when Right(`Entry Store`,5) = 'VAC"}' then 'VAC' when Right(`Entry Store`,5) = 'SIC"}' then 'SICK' when Right(`Entry Store`,3) = 'OTH' then 'OTHER' end
you can vary what you are evaluating on as well. In the last when statement, for example, I am just looking at the last 3 character of the field. I could also look at a totally different field if I wanted. You can also add an ELSE statement just before end to deal with any scenarios you didn't account for, like this
case when Right(`Entry Store`,5) = 'PTO"}' then 'PTO' when Right(`Entry Store`,5) = 'VAC"}' then 'VAC' when Right(`Entry Store`,5) = 'SIC"}' then 'SICK' when Right(`Entry Store`,3) = 'OTH' then 'OTHER' else `Entry Store` end
Re: Reduce ETL Processing Time
@jmmc How may rows of input data does the flow have? I have an ETL flow with 1.4 million input rows that has multiple joins, some groupings, and a rank & window tile that runs in about 1m 30s. Do your inputs have a lot of columns? If you don't use all the columns, you might try selecting only the columns you need from each input. Same goes for filtering rows, if your datasets go by date and you don't think you'll need dates before a certain point you can filter out those rows. Also, are your joins just on one column or multiple columns?
Re: Reduce ETL Processing Time
@jmmc I agree that ETL v2 is probably your best bet. Joins are generally very processing-intensive, so it's not surprising that a dataflow that joins 17 datasets would take a while to run. I'm not sure if this applies to your situation, but you could also see if there are ways to filter the datasets as much as possible before joining them together so that there are fewer rows to scan in each join.



