Best Of
Re: Connections with other Domo Everywhere / whitelable companies and users
We are in a similar position and have just started using domo and domo everywhere's whitelabeled solution. Would be great to connect 👍
Jones01
Re: Formula for rounding time to nearest minute
I have a question about your example. Wouldn't line 12 get rounded to a different minute then line 13? Line 12 should be rounded to 01:04 while lines 13-15 should be rounded to 01:05.
Otherwise, I was able to use this formula to get to the nearest minute:
"HH:MM"
CONCAT(LPAD(trim(Trailing '.0' from FLOOR(ROUND((TIME_TO_SEC(`Time`) / 60),0)/60)) ,2,0),':',LPAD(trim(trailing '.0' from (MOD(ROUND((TIME_TO_SEC(`Time`) / 60),0),60))),2,0))
I then used a rank and window tile to get a row number for each "HH:MM" value from the above formula. Then I filtered the data for Row=1 to only return one line of data for each HH:MM.
The idea behind the formula is to convert the time value to seconds. You then divide the number of seconds by 60 to get the number of minutes. This will now have a decimal for the fraction of the minute represented by seconds which can be rounded to get to the "nearest" minute.
Re: Filter to Compare on a table different years but same period of time?
@jaeW_at_Onyx here's a breakdown of how my card is set up that makes it work.
I create a "standard date" beast mode field that takes the date field in the dataset that you need to do YoY on and moves it into the current year.
DATE_ADD(`datereported`, interval (YEAR(CURRENT_DATE())-YEAR(`datereported`)) year)
My year field is just extracting the year from the date field, which can be used for the series (or rows in a pivot table.
YEAR(`datereported`)
I create a quick filter that allows me to easily filter how many years back I want to look at with this beast mode:
YEAR(CURRENT_DATE()) - YEAR(`datereported`)
The date range filter is based off my "standard date" beast mode which is why it will always show the current year in that range, but that year is actually meaningless. The Graph by is more important so you can choose what granularity you want to compare against.
Here's what it looks like as a pivot table.
It proves to be quite flexible using the quick filter to let you decide how many years you want to look at.
Re: Filter to Compare on a table different years but same period of time?
@MarkSnodgrass i was flipping through your tutorial. in your proposed solution the DateFilter is set to This Year + a couple extra years via YOY comparison option.
as best you can tell, is Domo actually applying the DateFilter filter? I'm guessing not b/c Domo ought to be limiting you to either just this year, or the last n years per the DateFilter selection.
@GrantSmith 's approach is a lot more effort to get off the ground, but once you get it, it's a much more extensible and guaranteed to work every time solution, IMHO
Re: Filter to Compare on a table different years but same period of time?
I created a video that shows how you can create a standard date, which then allows you to look at different years next to each other. My video uses a line chart, but you can switch to a pivot table and format the date fields as needed to get the look you want.
Re: how to break a week between months
@WorldWarHulk Here is an alt approach - I used Magic2 for this example:
Note that my Date column is labelled Date && my week starts on Sunday ends on Saturday.
Also, it assumes that crossing months defaults to the first day of the later month - thus 10/1-10/1 and NOT 9/25-9/30 ( the week would be defined as 9/25->10/1 you can handle this in the case statement by checking whether the number of days is greater in the prior month vs later month for Cross Month conditions and select which label you want to apply).
Using A formula Tile:
FirstDayOfWeek: date_add(`Date`, interval -WEEKDAY(`Date`)-1 day)
LastDayOfWeek: date_add(date_add(`Date`, interval -WEEKDAY(`Date`)-1 day), interval 6 day)
Cross Month Boundaries: case when MONTH(`FirstDayOfWeek`) = MONTH(`LastDayOfWeek`) then 0 else 1 end
Label:
case
when `Cross Month Boundaries` = 0
then CONCAT(`FirstDayOfWeek`, '-', `LastDayOfWeek`)
else CONCAT(DATE_SUB(`LastDayOfWeek`, INTERVAL DAYOFMONTH(`LastDayOfWeek`)-1 DAY), '-', `LastDayOfWeek`)
end
Hope this helps!
nikky
Re: Request for Topics
- How to optimize data pipelines in Domo (DSV, Magic 2.0, Upsert connectors, etc.)
- Dashboard design best practices (What makes a dashboard stand out? How do you tailor your dashboard to the intended audience?)
- More Domo Everywhere content!! This feels like a black box at times, as I haven't seen very many public-facing training videos on the topic.
Thanks Professor!! Love the new video!
ellibot
Re: Request for Topics
- Account Management best practices, any tooling to manage accounts.
- How to manage POCs, DEV, and Prod pipelines in Domo.
Re: Request for Topics
- +1 on Account Management. I have spent a ton of time creating dashboards to audit my instance (more advanced than just DomoStats). In order to monitor what is coming in, going out, and managing users (especially across multiple instances). Learning how/why to create custom roles would also be a good part of that.
- +1 on Domo Everywhere content. Best practices for creating published jobs would be good. Especially since each job creates a new federated dataset. I made a mess when I started and now I have to clean it up 🙃
- How to utilize new features once they come out, I always struggle creating content for my users regarding new features so then we just don't end up using them for a while. Having some concrete examples would be useful (ex. I never got to using Segments and I still couldn't tell you how to use them).
- Best practices for instance health. I have so many users creating so many flows and rows of data that could be much more optimized. Going over Magic ETL best practices for a clean instance and quicker run time would be useful.
- Creating alerts to manage data. This is one I learned to do myself by doing error checking in flows to create error datasets, making error checking cards, and more recently just putting alerts on a dataset. Knowing your data is wrong before it has time to make it to the end user is very useful.
Ashleigh