Best Of
Re: Extracting the Date Based on a pattern
- check for the * character in the string
- if present then get the last 10 characters from the strings (if always is the date at the end)
- convert it to a date format month , day and year
- if the character * is not present then use the other column
This beastmode should do the job
-- name your beastmode Soldorstockdate CASE WHEN INSTR(`orderstatus`, '*') >= 1 THEN DATE_FORMAT(RIGHT(TRIM(`orderstatus`),10),'%m/%d/%Y') ELSE DATE_FORMAT(`orddate`,'%m/%d/%Y') END
Godiepi
Re: Checking if first character is a *-Beast mode
If you are only looking at the first character in a string you can use the LEFT function, like this:
CASE WHEN LEFT(`orderstatus`,1) = '*' THEN 1 ELSE 0 END
Re: Writing Beast mode with Data label of Measures
Try something like this
CASE WHEN SUM(`Open qty`) > SUM(`onhandunits`) + SUM(`openpoqty`) THEN 1 ELSE 0 END
Re: Drill down to a separate dataset - matched by column?
Hi @svetlana
You can use a different dataset in your drill path card however if you wish to have the filter applied to the drill path card your filter field needs to be named the same within the two datasets.
Re: Drill down to a separate dataset - matched by column?
@svetlana do you have any filters applied in your top level card on columns that do not exist in your drill path card?
This has tripped me up before - when you drill down all the filters from your top level card are carried through (even though you don't see them explicitly) so if any don't exist on your drill path card dataset, it won't work.
mhouston
Re: How does the dashboard level filter work?
When you configure a card, if you're displaying multiple dates on the axis, you can choose which column you filter on based on the Date Range Field.
Typically the field will default to the first field you show on the card.
Re: OR statements in card filtering
In a word, it's not possible.
Domo does not support filtering across rows for "or"
What you could do is create a pipe delimited list for all the datapoints per user
eg.
AllPoints = 'green|circle' then when you filter you can search for "green" and then search for "circle" and choose the one that overlaps.
if you have too many options this becomes cumbersome. Make sure to create your pipe delimited list sorted in alphabetical order so that
"green|cirlce" == "circle|green"
Re: Default Date Filter on an Embedded Dashboard
@Airwon48, no your description made sense. you currently can't have a filter enabled (which excludes data) and then filter on excluded data.
That's why you'd use the default page filter, sorry forgot to link the KB, https://domohelp.domo.com/hc/en-us/articles/360042923914-Applying-Page-Level-Filters-with-Filter-Views
users would then have to deselect the default filter and then look for something else.
Re: Default Date Filter on an Embedded Dashboard
To meet your first requirement, you can set a default filter for a page.
If you're doing it in ETL you might have a "isMostRecentWeek" binary column (a 0 or a 1) and then by default always filter to 1.
To accommodate your second requirement, we always recommend configuring a date dimension with a week column (i assume you mean week of year). You do have to be careful with beast modes because the start and end of the year can be tricky (when do you start counting the first week of the year? it differs by company).
Re: Beast mode help - a count of users who transact once a month in each of the last three months
@MarkSnodgrass i love that! but it'd only work if you kept customer_id on the axis. so you'd see each customer and then be able to filter or see if they have the count = 3. but if you just wanted one number it wouldn't work.
at this point it may be easiest to make a summary dataset with the granularity of one row per user per month and a binary flag if they transacted, or total transactions (could create this as a dataset view). from there your count distinct calc and accompanying viz would be trivial (CASE statement or filter as Mark suggested)