Best Of
Re: Dynamic Target Based on Current Date
Your beast mode syntax should look something like this:
(CASE WHEN CURRENT_DATE() >= '1/1/2022' AND CURRENT_DATE() <= '3/1/2022' THEN 98 WHEN CURRENT_DATE() >= '3/2/2022' AND CURRENT_DATE() <= '5/30/2022' THEN 98.5 END )
You might also consider adding an ELSE clause to handle when the current date doesn't match any of the WHEN clauses.
Re: Moving one column under another
You can do this in Magic ETL with the Unpivot tile. If you are unfamiliar with it, you can read about it here:
https://domohelp.domo.com/hc/en-us/articles/360044951294-New-Magic-ETL-Tiles-Pivot#3.
Re: Help with Magic ETL to calculate the distinct count of pickup numbers by plant
instead of materializing this using a bunch of CASE statements consider just building a pivot table card in Analyzer.
Re: Beastmode Cleanup
It depends if you're deleting a beast mode that's saved to the dataset or not. If you delete one from the card that isn't saved to the dataset then it's just that card.
There isn't a simple way through the UI to get the duplicated beast modes however you can utilize the DomoStats / Data Governance datasets to get the cards and beast modes datasets which should have the beast mode definition and if it's saved to the dataset. You can then pull the powering dataset from the card dataset, group by the dataset and see how many records where the name and formula are the same and if there's more than one record you have a duplicated beast mode.
Beast Mode Manager will archive off the beast mode and remove it from view. This is better if you want to be able to potentially recover the beastmode at a later time.
Re: Microsoft SQL Server Partition Connector
that's a shame.
you can however use the Java-CLI to push your own partition tags. so if you must partition on non-date columns, the CLI may be your best choice.
Re: Historic Timesheet Analysis
@mhouston you probably can't automate allocation.
you could try building buisness logic.
so like if the amount posted is negative then just subtract it from previous entries (so we operate on the assumption that we aren't back posting two or three week ago adjustments).
this might help you smooth out the negative spikes ... but also assumes that in your -40 hours example that we need to adjust out the 22nd, 21st etc.
alternatively you could use Domo as a business process for capturing the why adjustments were made if your ERP system doesn't support capturing 'reason codes'
so you could use a webform (or form builder or any other data entry tool) that requires users to justify why a negatvie entry was made (alerts). ie you'd need an "applies-to" field to say -40 hours applies to entry 36, 37, 39
THEN run an ETL that produces an 'adjusted dataset' where you GROUP BY entry_id to apply the allocation.
Re: Historic Timesheet Analysis
@MarkSnodgrass thanks for the ideas! Your point about training accounting is a good one and this is probably a good opportunity to revisit the time entry business process and see if we can put better controls in place.
mhouston
Re: Waterfall Chart colors
Not sure if maybe the feature wasn't available when the question first came up, but you can simply use Chart Properties to change the color of each Waterfall bar.
Unknown
Re: Sorting Year date Filter in Ascending order
Quick filters to do not pay any attention to the sorting properties, unfortunately. They are treated as strings and will always sort ascending. Your best bet is to have your values be Year-Month, with the month always being 2 digits. You can do that like this:
DATE_FORMAT(`datefield`,'%Y-%m')
This should return it as 2022-04 for April 2022.
Re: How do I determine what dashboards use a given card?
You can use the DomoStsts connector to get the Cards and pages dataset which will tell you all the cards on a page