Best Of
More role permission granularity
There needs to be more granularity around the permissions that can be assigned to roles - specifically regarding the permission grants offered for Role and User management. There needs to be alternatives to the current 'all-or-nothing' options of 'Manage all roles' and 'Manage all users' permissions.
I created a custom role with limited admin access. I need this role to be able to assign new and existing users to roles other than Participant. With the options currently available, they cannot do this unless I assign them to the Privileged role (which lacks other permissions they need and would only allow them to assign new users to other roles) or I grant them full access to role administration ('Manage all roles'). However, granting them 'Manage all roles' would grant them far too much access, including the ability to elevate their own permissions or remove mine. They also need to be able to edit attributes of existing users, but that is only currently allowed by the ‘Manage all users’. Again, this grants the user far more permission than they should have, including the ability to delete Admin users.
There needs to be a way to define a hierarchy among the roles (which includes Custom Roles). Then, an ‘Assign Roles’ permission (that has no access to create, edit, or delete roles) needs to be created that allows users assigned to that permission to manage role assignments within the following restrictions:
-The ‘Assign Roles’ user can only change role assignments for users currently assigned to a role less than or equal to the ‘Assign Roles’ user’s role. This prevents them from removing permissions from a user with more elevated access.
-The ‘Assign Roles’ user can only assign users to a role less than or equal to the ‘Assign Roles’ user’s role. This prevents them from elevating their own access.
My proposal regarding permissions for ‘Manage all users’ is very similar whereby a limited ‘Manage Users’ permission would be created that allowed users with this permission to Edit users and reset passwords for those users whose role is less than or equal to the ‘Manage Users’ role. I could even see a need to making the 'Reset user password' into a standalone permission.
Release Notes - What Changed
Many times new releases add additional things which aren't documented and can silently break dataflows and metadata which we rely on to properly administer our instance. Can we get a list of things that have changed in the release to see what issues we might be running into when monitoring our instance? Could we also get this ahead of time to make sure we can prepare for the new releases?
App Studio Controls/Filters
While creating apps with multiple pages/tabs we don't often use the same dataset for each card we put on a dashboard (app in this case, woohoo for app studio!)
Where we are running into trouble here is that page filters only have the option to select a singular dataset rather than all datasets where the field is present.
Even better, we would love to be able to apply a filter, with all datasets that field is present in, at the app level rather than on a page by page level within the app.
Add true card view reporting
With current DomoStats reporting we are missing the ability to track clicks on a card from a page. A Card will be reported as Viewed when the user clicks on the name of the card and actually opens it, but not if they expand the card (i.e., via Story Presentation Mode or via Story Presentation Mode via Next/Previous control) or drill into it or export it. We understand that a count when someone just looks at a card on a page could be hard to capture, but an actual click on the card should be counted as a view.
As mentioned above, Drilling into a card on a page does not report back in the DomoStats Activity Log as a View of that Card, or a Drill. If you use the Drill in Place functionality you do not have any visibility to who is actually using that capability.
This idea/request is to count any click on a card in a page as a view in the DomoStats Activity Log. That would be the minimum request, but ideally the addition of type would be nice to show how the click was made; drill, expand, export, detail…
The inability to truly see card usage from a page is a huge miss for us when it comes to user accountability.
Add A Tile To The Dataset Overview That Shows The Dataset Views That use This Dataset
In the highlighted areas include the dataset views that use this dataset. In the "Direct Impact" section add the count of dataset views. Also add a new tile that that shows the dataset views that are created and gives the option to create a new one. This should be similar to the tile for DataFlows.
Smart Text to allow formatting of Date Variable
Currently if you use a date Variable in Smart Text it is limited to YYYY-MM-DD format (or per locale). If would be great to be able to format based on criteria, including fiscal formatting. e.g. For 31/12/2022 it would be Q2 FY23.
April 2024 Community Forum Highlights
Hello Domo Community!
How is it already May?! Nonetheless, it’s time to post the April Community highlights. The Community has been growing steady over the course of the last year, and it’s showing! Discussions, posts, and reactions have 4x what we’ve seen in the past. And every single question asked on the Community Forums within the last year has gotten an answer. That is ZERO unanswered questions in the past year! We will be celebrating this accomplishment with the Community in the near future. Stay tuned.
Leaderboard Top 3
This month’s leaderboard is not a shocking list, but we never overlook your efforts! Huge thank you to some of our Community’s KEY members. You are so helpful.
- @GrantSmith 530 points
- @ArborRose 519 points
- @ColemenWilson 382 points
Top 3 Posts
Of the 289 discussions that were had in April, these three got a lot of views and engagement. Follow the links and leave a reaction if you found them helpful too.
- How to get the first character of a string in domo beast mode analyzer
- Case Statement – 28 days from a specific date?
- Scheduled reports, permissions + PDP
Huge shoutout to the following community members for asking such great questions and finding even better answers: @Jones01 @ColemenWilson @pauljames @david_cunningham @Utz @jessdoe @GrantSmith
Top 3 Ideas
The Domo product is always improving because of your ideas. Below are the ones that got the most votes. Click the links below and give these ideas additional upvotes to increase their chances of getting implemented into Domo.
Congrats to these community members for coming up with innovative ideas: @Kunal @erikjamesmason @DashboardDude
April Community Member of the Month
@david_cunningham, we have felt your energy since you joined the Community Forums at the beginning of this month! In less than a month, @david_cunningham started from zero points and ranked up to be a Contributor. At this rate, you’ll be a Coach in no time 😉 @david_cunningham, thank you for contributing to the Forums! We’re excited to have you and see what you do next.
Like this post if you've been enjoying the monthly Community highlights. And make sure to welcome and congratulate @david_cunningham in the comments below 🥳
App Studio - App deployment via Domo Sandbox
Ability to deploy apps created within App Studio via Domo Sandbox
Tool to convert MySQL data flows to Magic ETL
In order to take full use of the power Magic ETL v2, it would be great if a tool could be developed to take a MySQL data flow and convert it to Magic ETL
how can i track remote domo stats available in my child instances (05875821)
apparently remote domo stats have to be enabled on a per request basis (ticket 05875821)
if i have 100 instances, what would be the most expedient way of confirming that all of them have the same stats reports available?
if Domo updates a version of the report (and modifies the schema or how content is generated) what would be an expedient way of knowing which instances are producing different versions of the report?
Is there any way for me "just a business user" to not have to manage that process?