Best Of
Re: VIDEO TUTORIAL: How to calculate Percentile Rank (for A/B testing)
This was so helpful Jae! Thank you!!
Re: Cards - BeastModes Need to Know the Dates that are selected by the user (card/dashboard level)
@ttronson As far as I'm aware, Domo does not log the specific filters that users select. I'd recommend posting this to the Ideas Exchange as an enhancement to the Activity Log or DomoStats.
Re: How to Aggregate DateTime Differences
@JedP - this is great. Thanks for sharing.
@AnnaYardley - this seems like the kind of post that might make a better blog post then a Dojo topic as it really isn't a question, just a well thought out solution to a common problem.
Re: Calculated Column using Current Date
@JenHarrison It looks like your missing a ) after CURRENT_DATE which is resulting in the syntax error. Though you will probably want to use the DATEDIFF() function instead as in your current beastmode it's just subtracting the day of the month so you might run into situations where it results in a number greater than 6 but it is actually within 6 days. DATEDIFF() will give you the number of days between two dates.
Re: MySQL Workflow
@ArborRose That makes sense. You can also limit which columns you need to load from your input dataset to reduce the amount of time to takes to load.
That said, I've found that MagicETL v2 can handle some fairly complex transformations and is generally more efficient than MySQL. Ever since Domo upgraded from the previous version of MagicETL, the only times I still need to use SQL dataflows are for use cases with complex join criteria.
Re: REGEX Extracting Names
I would use the formula tile and use the replace function multiple times to remove those characters.
Something like this:
REPLACE(REPLACE(REPLACE(fieldname,'[',''),']',''),'"','')
Re: MySQL Workflow
@ArborRose Although you are limiting your rows in the transform, Domo's SQL-based dataflows still need to load all rows of the input datasets before executing any transforms, which explains why it is taking so long. For something as simple as what you're trying to do, I'd recommend using a Dataset View or MagicETL instead for better performance.






