Best Of
Ability to default "Show description on card details" to be checked
Currently this defaults to be unchecked for all cards created. This seems backwards to me. If I am adding a card description, it is because I want users to have a description of the card they are looking at. Hiding this by default doesn't make sense. In the past, showing the description was the default, as can be seen by this old post: https://community-forums.domo.com/main/discussion/56361/can-we-default-the-show-description-on-card-details-to-be-unchecked-in-our-instance-please-this?utm_source=community-search&utm_medium=organic-search&utm_term=Show+description+on+Card+Details
This request is to either default to show card description (as it used to be), which makes complete sense to me. Or to give the option to give admins the choice in Company Settings in Admin.
Allow dataset schema definitions to be published
With the ability to publish AI Readiness from a dataset in one instance to another, the dataset's schema definitions should also be publish-able.
This will allow us to set the definitions of a dataset from within our main dev environment and the end users within our prod environment to see those definitions inside analyzer. Currently we can set the definitions within our dev environment, but they disappear once we publish that dataset. We want to be able to provide as much context as possible where our end users are actually building their cards.
No Credit Charges for DomoGov/DomoStat Datasets
I'm an avid believer in utilizing business and technical metadata to train, govern, and administer business intelligence. The primary reason for selecting Domo for my new company was it's ability to visualize the full-stack data journey (Connect→Warehouse→Transform→Visualize→View) through metadata. This became the focal point of my KPI's, and helped proactively identify the who/what/when/where's.
Now that the Domo environment is consumption based, it no longer allows me to have live insights into users and data journeys. The activity log provides a granular detail level, but much more difficult to visualize and drive actions from compared to custom dashboards.
I'm hoping that Domo can make an exception for charging credits on DomoGov/DomoStat connector datasets, considering they are pulling internal data around the instance. =)
RWalsh25
Link to tab within an app studio page
It would be very helpful to have a way to direct to a tab within an App Studio page. Both as a URL and as content to open via an action:
Allowing pop-ups within an iFrame
Under the current security settings, we can't drop previously built visualizations within an iFrame from external systems (like PowerBI) as the sign-in button requires a pop-up in order to authenticate. It would be great if we could allow pop-ups to populate within that iFrame Domo, and allow us to sign in to the external vendor, thus keep existing security settings while allowing us to access the content.
Re: View as user or view as role
Hi, @JasonAltenburg, @DataMaven, @afranklin, @Kyrsten and everyone. Thank you all for being engaged in the Community Forum and for posting here in the Ideas Exchange!
While I know this particular ideas thread is about "view as", we've also heard feedback that there are use cases for taking action as another user: "act as". Here's a hypothetical use case: "I want to create a carefully curated experience for our new CFO that we're onboarding to the Domo platform. Of course I want to make sure they have access to all the right apps and data; but I also want to validate that they have the right role/grants to use Domo the way they need; and I want to add a few important cards to their Favorites."
I've appreciated the opportunity to talk at length with some of you about this and with your help I think we've found a good path forward; Let me provide some insight into how we're approaching this.
We're still working through some solution design considerations, but we're hoping to move forward with User Impersonation. This new capability to impersonate another Domo user would be limited to admin-type users (controlled by a new admin-level grant), and start/end and justification for impersonation would be logged. During the time-limited impersonation session, the admin-type user would be able to both view Domo as the user, and also act in Domo on that user's behalf.
Using this approach, we would be able to address both the need to view and act as another user. And while it may seem counterintuitive, we believe this is also our most efficient approach. So, don't worry: we wouldn't be delaying "view as" while we build "act as".
Finally, I imagine some Domo customers may not want to allow this functionality at all. For those customers we'll be able to entirely disable the feature.
That's a wall of text. If you made it this far - thanks for reading! Obviously, please feel free to share additional ideas and feedback here. I'll try to provide updates, too. And again, thanks for being part of the Domo Community!
Card Name vs Card Title (for cards that have the same title)
I manage multiple brands in our instance and we use different datasets and have different data points for our brands, but a lot of the cards have the same title. When searching for a card to add to a dashboard there is no way to see what dataset the card is associated with. I think it would be great if we could give our cards a name that is different from the card title, so it would be easier to identify which card goes with what.
ChrisLombard
Add a visual indicator to Drillable cards
It would be great if cards that had drill paths enabled had some kind of badge or visible indicator that would communicate to the user that there is a drill path enabled on the card.
Right now the only way to know is to try clicking on the card. A lot of functionality and usefulness can end up being hidden behind what looks like a normal card.


