Best Of
Re: I want to fetch count of data for a specific time frame (mon-fri)-(9-17)
@dheeraj_sandhanshi You can set up a beast mode like this to segment what data to filter:
case
when DAYNAME(`DateField`) in ('Saturday','Sunday') then 'Exclude'
when HOUR(`DateField`) >= 9 and HOUR(`DateField`) < 17 then 'Include'
else 'Exclude'
end
Re: Customer's Company email is changing what needs to be checked to ensure no issues after the change?
We recently went through the same thing and we just went in and changed all of our user's emails after the switch. You should be able to use the bulk import feature. I recommend exporting a list of all your users and then auto update all the emails and then reimport it. Definitely agree with @trafalger, always have a couple people on the direct sign on list.
I also use the domostats datasets to alert me anytime a new user logs in so that I can catch email changes. Several times I have caught someone with a name change or email change that I knew had an account but I was able to see it from this alert. Once I see it I just go in and update their email then remove the old account and notify the user.
Ashleigh
Re: Customer's Company email is changing what needs to be checked to ensure no issues after the change?
Also 100% put yourself and whomever else would need emergency access on the "Direct Sign-On" list so you can still login to fix things. Also this URL is your friend
https://<subdomain>.domo.com/auth/index?domoManualLogin=true
Re: Customer's Company email is changing what needs to be checked to ensure no issues after the change?
@leonbrooks The primary email address associated with each user's Domo account needs to exactly match the email address used by your SSO provider. If the old email addresses are still going to exist as an alias, then I would suggest using the old email address as the alternate email for the Domo account as a backup.
Re: Preview flow "from here" option?
As @GrantSmith said, this feature doesn't currently exist. However, you can do what you want to do by breaking up your ETL into smaller ETLs for testing. Then, once you have it all sorted it out, you can copy and paste the tiles back into your main one so that you have a single ETL for production.
I would create a ETL Phase 1, for example, that does all the grouping work that you are referring to and execute that ETL. Then, create ETL Phase 2 and attach your Phase 1 output dataset as the input dataset of Phase 2. This should allow you test a bit quicker.
Re: Being Able to Change Default Colors
They have brand kit, but from what I understand, it makes you lose all of the standard colors. It would be amazing to have an additional row of colors that are custom for the instance so that branding can be done without messing up every existing visualization. (Which is what happens currently.) Plus, this should not be an additional expense.
Re: Trying to calculate Rolling Averages/Sums over the previous year
You'd have to do this in the dataflow -basically join the 12 prior monts to each month (Aka, April's date would have the prior 12 months appended to it and all have a "Report Date" of April, so in analyzer when you select April you'd have the 12 months there). If you don't want the ability to drill, you could aggregate this before appending it.



