Best Of
Column Level Permissions
Hello Product Team,
I have a use case for bringing HR and Payroll reporting into Domo, however, company policy has many permissions/accessibility protocols in place to protect PII data.
We are hoping that at some point Domo comes out with functionality for column level permissions (column level security) as well as integrated/live updating permission groups.
Please consider this for a future roadmap item.
Thank you!
Casey (on behalf of Telus)
Choose What Cards to move to a new dataset
The functionality to move list of cards from one dataset to another is great, but it would be even better if you could choose exactly what cards you choose to move instead of all or none.
rockchalk629
Extended DataSet information on DOMOStats
Can we get DOMOStats to include some of the additional information available on cards like in the API or CLI?
While DOMOStats is great, there are some key funcionalities it lacks that are already available through the API and CLI and that would be a huge help when it comes to managing the instance. Some of the top of mind things would be:
- Show when a card is using Fiscal Calendar or not
- To include information on DrillPath Cards (currently not visible)
- Show information on how cards are connected via drillpaths
- Show whether the drillpath is enable to go down to the dataset level
This way it'd be easier to identify which cards might need to be updated to align with company standards.
marcel_luthi
Card Delete Warning if Card Lives on Multiple Pages
When Deleting a Card in Domo a warning pops up saying:
Are you sure you want to delete Card? Doing so will delete this card from this and all other pages. This action cannot be undone.
I would like for this warning to be updated to actually include the # of pages the card is associated with. Typically our cards are just on one page so it can be easy to ignore the above warning and delete. The current best practice is to always check how many pages are on the card by selecting "Move Card" first, but that extra step is annoying.
user08845
Re: Why does dataset views count as storage?
With Row under Managment we charge credits for every 1M rows of materialized data in Domo. With that we include an additional 2M of virtual data (views or fusion). Most customers wont pay anything additional for their views, because their virtual data is less than double their materialized data. In the case that a customer doubles down on views to prevent paying for storage, or creates large fusions with Billions of rows, then we need to be able to capture some revenue there because we incur costs.
RJTracy
Re: Difference in Business Hours
I think I have something for you to get your started.
/* check to see if the start hour is too late */ (CASE WHEN HOUR(`startdate`) >= 17 THEN ((UNIX_TIMESTAMP(`enddate`) - UNIX_TIMESTAMP( /*move it to the next day and start at 9 */ ADDTIME(ADDDATE(DATE(`startdate`), interval 1 day),9*60*60))) / 3600) ELSE /* subtract and then divide by 3600 to get the hours */ ((UNIX_TIMESTAMP(`enddate`) - UNIX_TIMESTAMP(`startdate`)) / 3600) /* if there is a difference in days, subtract 16 hours per day */ - (DATEDIFF(`enddate`,`startdate`)*16) END )
You will need to add some additional case statements to deal with weekends by using the WHEN WEEKDAY(startdate) IN (1,7) which is Sunday and Saturday as I wasn't sure how you want to handle those. Hopefully the above makes sense. For a deeper dive into unix_timestamp, you might want to look at this post.
https://dojo.domo.com/discussion/52682/domo-ideas-conference-beast-modes-time-difference-formatting
With my testing this is what the above beast mode produces.
Hope this helps.
Expand the limit of tooltip fields
Hi! We are migrating a visualization from Tableau to Domo.
On Tableau, this viz has 14 tooltip fields.
Domo limits us to 3 tooltip fields.
It would be great to have a higher number of tooltip fields!
Marcello
Set Default Email Notification Option to Disabled
Our organization uses Domo Everywhere platform embed into our clients' portal, being the only way for our clients to actually access their instances. Therefore there is no need for the client to receive any email notifications from their Domo instances for any activities such as page sharing, scheduled reports, alerts etc as these email notifications will inherently have deep links in the email content (via buttons, charts or hyperlink text) which takes the user directly to their instance as opposed to via the right channel which is the client portal.
Is there a way to permanently disable email for the following scenario:
1) Page/Card Sharing - Can only share to an existing users in the instance with no email notification option
2) Schedule Reports - Users can receive the reports as an email content but no deeplinking to the page url of the instance
3) Alerts - Received alerts via email and again no deep linking to the card url in the instance
Re: Filter to Last 12 Months (dynamic)
I had a meeting yesterday with Ryan Moody and Zack Cameron from Domo and I took the opportunity to ask them for help. They gave me the solution!
In am posting this in case others have the same question.
Here is a short video I put together that provides the solution.
Please hit "LIKE" if you agree using videos like this is a good way to communicate.
swagner