Best Of
Some negative impacts of the new feature merged beastmode
Hi all,
Recently there is a newly added Domo feature where the 'Merged from datasource..." beast modes will be created when cards that are using the beast modes are moved to a new DataSet.
But we found that this new feature has an effect on the previous data source as well : domo will rename all the beastmodes merged previously (as "name + merged from xxxx") even if we have already adapted their name before and generated automatically another beastmode with the origin name... I understand that this feature allows the future merged cards to still render without errors, but it does make it more difficult from a governance standpoint for the previous merged cards.
As far as I know, we don't have a way to avoid this behavior, so we have to archive/rename all the beastmodes affected as necessary. But we really wish there will have an option to disable this behavior because il will cause us to waste time in some cases.
Thanks for your help,
Yinchuan
App Studio - Move/Copy Card Functionality
I love that in the Admin > Cards area it now shows "Dashboards and App Pages" for card locations.
A further "nice to have" enhancement would be to see the App title listed under Move/Copy when looking at a cards settings.
In this example- I know this particular card is both in my overview and on our Analytics Hub app. However, when I select Move/Copy on that card, it only shows my overview.
This is potentially a user problem more than a functionality problem but sometimes whether during maintenance, decommissioning old content, or reviewing content- we will reference the move/copy section to quickly determine impact on the users. If we looked here without checking the admin side, we could potentially be leaving content in an app that we intended to remove, OR deleting content thinking it may just be in my personal overview and not existing in an app page.
(example attached)
Thanks for reading that long winded explanation! Haha
I hope your coffees were perfectly crafted today!
Year Over Year cards Leap year issue
YoY cards cards where Year to date is the range set for the card do not calculate prior year totals and hence yoy changes correctly until the month is complete. Since a year is assumed as 365 days for YOY cards, the leap year throws off the comparison to prior years until the month is complete. We are relying on mid month stats very heavily, so having correct comparative numbers is crucial. A fix for Leap years needs to be developed to overcome this issue. Please up vote this.
Delete/Edit Cards in Bulk based on "Last Viewed" Filter
For admins, it would be great to be able to sort cards by the time they were "Last Viewed" and select them in bulk to either edit or delete them all at once.
We have thousands of unused cards but there is no easy way to filter them based on the last time they were viewed, which is a field/tracker already built in Domo. This would be perfect in MORE -> ADMIN -> CARDS, then have an extra column showing when the card was last viewed and be able to filter it like the other fields in this screen.
Seems like it should be such a simple feature to add but would help a TON with basic data maintenance and keeping our org clean and more organized.
DomoStats dataset - DomoEverywhere subscriber instances
I would like a DomoStats dataset listing all my Domo Everywhere subscriber instances/organizations. We can see the list of instances in the UI but can't export them. We can extrapolate a list of instances from other governance datasets (like activity logs), but this would only capture instances with data in those datasets. This would be useful for ensuring that the correct instances are active and filtering governance datasets to data from currently active instances.
Allow sorting of quick filters
Currently, we have many academic years in some reports but usually need to sort by the newest. However, all the order academic years are at the top of the filter and we need to scroll down the filter to get the current year.
Having the ability to sort this so the data currently on the bottom would be on the top would be extrememly helpful and help efficiancy.
ETL snap to grid
I like to keep very neat or orderly ETLs. Would love the ability to align ETL tiles horizontally or vertically or snap to grid or something. I think that would help keep a clean workstation.
Domo Feature Request: Allowing Users to Promote a Repository that contains locked beastmodes
We have many beastmodes that are locked on cards. Thus, only admins, beastmode owners, or those with "Manage All Cards and Pages" and "Manage DataSets" grants enabled. We are running into issue where users are unable to promote to our production environment because they don't fit into one of the three above categories. We want to enable departments to promote content that contains locked beastmodes, but we don't want them to have the ability to edit them or have access to manage all of our datasets.
Set the default value of date type Variable to current date or today's date
A date type variable needs to have a functionality where the default value can be set to today's date
Preview Window Limits in Magic ETL
There is currently a 100 rows preview window limit when you do the preview run on the ETL. We need to increase this as it can help drastically with further work in the MagicETL.