Best Of
Re: Overhead in Financial Statements
@Data_Devon Here's a video on Group Bys:
Also you may need to use Fixed By to help out:
Re: Workflows - create dataset?
@Sean_Tully this definitely sounds possible with workflows. You can create a variable from the form input and then use the query dataset action and use your variable in that.
ellibot
Re: Unable to add new filter in App Studio though being owner
We had this same issue and submitted a support case and Domo got it resolved this morning. So if you check now it should be fixed.
Re: Drill to final dataset report
@James_Lord I think your dynamic parameter and URL are a bit off. Here's what my config looks like:
ellibot
Re: Overhead in Financial Statements
We can't see the end of the formula.
SUM(CASE
WHEN condition THEN value
ELSE value
END)
So it would be
SUM(CASE
WHEN `Account` IN ('EE Salaries and Benefits', 'OD Salaries and Benefits', 'Supplies')
THEN `Amount`
ELSE 0
END)
Without the THEN value in there, there is nothing for the SUM() to act on.
Edit…and whatever that other 'XXX' is at the end of your scrollbars.
Re: The Comparative Gauge chart is showing the % change incorrectly
I did a quick test with a current value of 4000 and previous value of 0 does result in a comparative value of 4000 so it seems like this chart does not correctly divide by zero but treats it as 1 instead.
You could add some additional logic to your current value beast mode to be zero if your previous value is zero. This will result in a value of zero displaying in the gauge.
Re: View as user or view as role
Hi, @SarahR365, @AndrewMeierOptiv, @JasonAltenburg, @ellibot, @ColemenWilson, @afranklin, @Kyrsten, @DataMaven and all. I'm happy to let you know that we're planning to start development this month. (I know, it has been a loooong time coming - thanks for your patience).
As we're getting started, I want to update/remind you of our current plans for this feature and I also would love your feedback on one thing in particular.
Feedback requested:
Considering that impersonating another user is a high-privilege capability, I'm wondering your thoughts on an approval flow. Something like this: If I want to impersonate another user, I request to impersonate and provide my rationale; the person I want to impersonate gets a notification and can either accept or deny my request; if they accept, they specify how long their approval persists; then I can start an impersonation any time within the approved window.
Do you see an approval flow like this being value-added? Does it increase or decrease the likelihood you would use Impersonation? That is, does the added control create too much burden such that you wouldn't use Impersonation at all? Would your IT/sec teams consider the approval flow unnecessary, nice-to-have and confidence inspiring, or absolutely required? And finally, if we create an approval flow for Impersonation, should it be admin-configurable to require or not the approval flow in a given Domo instance?
Plans for this feature:
- Ability to impersonate is governed by a new admin-level grant, which will be included only in the Admin system role, but could be added to custom roles
- A user must provide their rationale for impersonating
- Time-limited impersonation session (60 minutes or max session duration for the instance, whichever is less)
- Impersonating user can act and view as the user they're impersonating
So, we're moving forward. Thanks for your interest and your feedback. And thanks in advance for your feedback on my specific questions about the approval flow. Looking forward to hearing from you!
Re: October Community Recap 🕷️
Amazing. I've had to learn the hard way to "under promise and over deliver". I too often OVER promise and get myself stuck.
Re: October Community Recap 🕷️
Biggest Data Horror Story
I can think of two. I was the sole author of an order system for a major company that supplies point-of-sale to restaurants. I accidently deleted the user table. When I saw the system message my heart sank. I'm pretty sure it skipped a couple beats. I managed to get the table rebuilt quickly and nobody was affected.
The other - I worked for a large school district (50+ schools). A contracting company was quoting a significant amount (equivalent to a person's salary) to perform an update. I balked and told leadership it would take me less than a hour. In the last hour of the day, my co-worker peaked around his monitor and smirked. With a grin, I responded "yeah, sure let's do it". It failed. Yikes. I thought my co-worker was going to have a coronary. I said, "stay calm, I've done worse {see above}". After a brief moment of thought, I modified a value in a table and it resolved the issue. Time to complete - less than an hour.