Best Of
Improve PDP on Domo Everywhere publishing
I have a suggestion for a product enhancement. The suggestion has to do with one of the steps in the Domo Everywhere publishing process. Specifically about the 5th step in the create or edit process of a publication job, the one where you choose the PDP policies to include.
Once you have more than a handful of DataSets included in your publishing job, it is difficult on this page to determine:
- Which DataSet(s) need to have permissions set.
- Which DataSet(s) may have more than one permission set.
- Which permission is set for each DataSet
The frustration mostly comes from the seemingly haphazard way that the list is presented, along with what appears to be technical limitations of the page that don't allow the browser's search function to work on that list (as it appears to load dynamically as you scroll, which means the data isn't there to search with the browser).
Ideally, it would be best to have the page organized by the DataSet for which permissions need to be set. Then, for each of those DataSets, you could choose which PDP policy (or policies, if it is intended/valid to have more than one) to apply. At very least, if the 3 columns could be sortable it would allow the information to be shown in a more logical order, customized to the need of the task at hand. Also, if each column were filterable or if the filter on that page were able to filter both the Policy name and DataSet column instead of just the Policy name, it would be very helpful.

Quick Filter Displayed on Dashboard or App
Could quick filters on cards become something users can interact with from the dashboard or app? Right now, a viewer can only interact with it if they expand the card—ideally we could toggle the quick filter being viewed in the "appearance" settings and any dashboard or app viewer could interact with it right away. Or the quick filter would appear when we add controls to the page.
It would also prevent having to make separate cards or variable/control workarounds for filters every time we want this kind of easy user interface on dashboards/apps we make

Magic ETL can use Federated Dataset
Hi,
We have number of cases where we want to use Magic ETL using federated Dataset. Can discuss them?
Thank You.
Best Regards,
Tejal
Schedule ETL for Last Day of The Month
We have an ETL that needs to run on the last day of each month. Our current solution is to run the ETL on the 28th, 29th, 30th, and 31st. Can Domo add a default Last Day of the Month option similar to the Last Day of the Month Option in the SFTP scheduling options?

Turn on Ruler and Gridlines in Dashboard Edit
Having the ability to turn on ruler and gridlines when editing a dashboard will be awesome for someone like me and my team where we usually design the dashboard from scratch instead of using the pre-built template.
This will enable us to align sizes and set sizes of each card more accurately because at the moment everything is guesswork and some times, the cards are not equal in sizing due to lack of ruler gridlines.
Dashboard Page Filter: Automatically set a default value based on the available values in the filter
When a PDP policy is implemented to a dashboard, I noticed that we cannot set the page filters (i.e. single select filter) to a default value for each PDP policy or have the page filter automatically set to a default value.
This is because when there are mandatory dashboard filters in order for the dashboard to work intuitively, these get broken by the pdp policy, resulting in end users seeing as though the cards in the dashboard are broken. In order to workaround this, I have tried creating filter views. However, even then the filter views are not able to default to specific users which defeats the purpose.

Enable AI chat only on specific Dashboard / Apps
Hello, I think it would be a helpful feature if we had the ability to enable AI Chat only on specific dashboards / apps. For example, only on production dashboards or only on specific cards that we feel confident having AI provide answers to our end users.

Require High AI Readiness for AI Chat use with Datasets
Hi, I think it would be a great feature to require datasets to have high AI readiness in order for AI chat to work with them. This would improve the results of the AI chat outputs and would create better data governance around the metadata and definitions. This should be a feature to be turned on/off by an admin of the tenant. Maybe it's tenant wide or maybe it's based on roles/groups.
