Best Of
Re: Dropdown fields / Data Validation via Webform
Is this still not a thing? Would be very useful right now! 🙃
Re: Multiple case statements
@NFerna When using the LIKE operator, be sure to use the % wildcard so that it matches values that that contain the letters "TVS" but don't match exactly. It should look like Variety LIKE '%TVS%'
Re: Create a date field from separate month and year fields
You can use the STR_TO_DATE function to achieve this in conjunction with CONAT. You can find the reference for available functions here:
So your formula will look something like:
STR_TO_DATE(CONCAT('01/',`Month`,'/',`Year`),'%d/%m/%Y')
Re: Incorrect subtotals on the cards
@Dev_ Subtotals of ratio calculations can show an unexpected result if the beast mode does not specify the aggregation. So, if your beast mode is Labor Cost / Labor Hrs it is calculating the ratio for each row individually and the subtotal aggregates the results. If you want your subtotal to represent the ratio of the other columns' subtotals, then you will need to aggregate each component individually within your beast mode like this: SUM(Labor Cost) / SUM(Labor Hrs)
Re: How do you change the field used for the date range on a card?
Some time has passed but Google suggested this to me, so dropping a comment for future web travelers who wrestle with a similar issue—grayed out date filter options.
My scenario was that one card (bar chart) displayed an x-axis with a calculated date, but the date filter had a different date column selected entirely. This was the desired outcome. A future built card using similar data would not replicate function because of the "default" behavior, as explained above in @mlb's note:
"As mentioned in the dojo article shared by you, I found out that, it is true. It is the functionality of Domo that, it uses the last date field added to your table card as the date range field but specially in table card. In case of bar chart, it always uses the date field which is in X-axis." and Domo claims it isn't a bug at all.
Well, that's sort of true.
For a bar chart, you can CAST the date field as a string with a DATE_FORMAT Beast Mode, and Domo charting then types and no longer overrides the date filter behavior. It's a situation where you have to unfortunately outsmart the tool, rather than the tool allowing the behavior and flexibility needed for design requirements.
What's even more confusing is the original card, the one I was trying to mirror, both the calculated date and the x-axis date were both typed correctly as dates, but this alleged default behavior was not applied. It's not clear if there's a secret handshake or order of actions to override the standard behavior, and it seems like a bug (even if we call it an 'escaped feature'). I'm not going to try to bark up that tree though — just cast display dates as strings and work from there.
Icing on the cake, Domo will (smartly!) pick up formatted date strings and allow date display strings under Properties to override, so you don't have to worry about y-m-d, m-d-y, d-m-y, etc. in pushing your string.
(Potential use case: Let's say you need to build a forecast each month that shows the next twelve months. You want to review last month's forecast versus this month's forecast using built-in date filtering, but all forecast dates are projected into the future. Domo, thinking its being helpful, blocks setting the date filter to 'Forecast Create Date' by defaulting to the displayed date of 'Forecasted Month'.)
Re: Capturing a calculation and add the result to a new dataset.
The first solution that comes to mind would be to build an ETL that runs on a monthly schedule. You can use the appropriate tiles to count up the accounts, and use a formula tile to capture the run date. You can set the Output tile to append the new data instead of replacing it, so you don't lose the historical counts.
Re: Applying Filter Tile to Remove Nulls Not Working
Hi @pauljames
I have had this happen to me twice in the past. The first time it was because the value wasnt actually a NULL but instead a blank. The second time was when I was actually trying to filter out blanks (not NULLs) and there ended up being an invisible character in my blanks that caused the filter to misinterpret things.
DomoDork
Re: Find and append a value to a field
You could do this:
CASE WHEN RIGHT(myfield,1) = '/' THEN myfield ELSE CONCAT(myfield,'/') END
Re: Word cloud in DOMO
Here is a video on how to break up comments into individual words and remove particular words.
Re: Additional Options for Multi-Factor Authentication
@AnnaYardley @GrantStowell can this be re-opened or does a new Idea need to be submitted?
