Best Of
Re: Tag dataflows automatically based on tags of output dataset?
In our case that doesn't really apply and in those few cases in which the dataflow does spit out multiple datasets, some of the tags will still be the same and I'd rather then remove one that is not relevant to an output instead of not having tags at all if that makes sense?
Re: Retrieving Data from a partner's Domo sit
@Mendoooza Check out the DataSet Copy Connector, which can be used to transfer data between instances
Re: Comparing weekly data
Totally agree, this is a headeache because the 1st week of each month does not have the same number of business days in it, and this clearly affects your metrics. The hardest part would be to come up with a name that everyone would agree for that standalone day, as it'll also need to be it's own standalone month as for not to give any special treatment to any of the other 13 🤔 (don't tell the others but I do have a preference for one of them already).
As for reporting right now, as soon as someone says they want to see weekly things in a Year over Year fashion, I tell them they'll only be able to see it as a comparison against 52 weeks ago, and that you cannot have a weekly view that aligns to month and year because of how Gregorian Calendar works 😅
Re: Bell Curve - Large Data
You can make your vertical card look more like a histogram by changing the bar width in the properties, that might be more visually pleasant for your use case.
Re: Dataset TimeZone Select
That gets dicey fast. Best practice is to leave your company time zone at UTC. That will minimize the number of datasets that require conversion in most cases.
Re: Average question
@shreeyab This largely depends on how your data is structured, but assuming you have one row per order you can use a beast mode like this and group by week:
count(`Order`)/count(distinct `Order Date`)



