Product enhancement ideas for Sandbox
I recently just found out that the global/page filters as set in your Apps Studio is not supported or included in Sandbox feature. I've been advised that the workaround is to manually apply the filters post Sandbox Promote. This is not sustainable especially in my scenario where there are 5 pages in my Apps and we have one…
For the Sandbox tool, the dev token used for authorization is set to expire every 2 years. This is too frequent, it would be great if we had options for it to expire every 5 or 10 years. Also, it would be great to have an alert that it is going to expire.
It would be great to be able to update the governance toolkit for virtualised datasets so you can edit a job so you can better organise specific groups of data into one job, rather then having to create separate jobs when new data is onboard at a later date.
It would be ideal for content committed and promoted via Sandbox to retain and deploy default filters
I would like the option to retain and remap tags applied to content when promoting from one environment to another in Sandbox. The ideal solution would allow users to choose which tags to bring over and to remap them if necessary. For example, in the source instance, a dataset is tagged as "ABC," but I want it to be tagged…
My company has 2 instances of Domo (Sandbox and Production). It would be super helpful to be able to change the banner color, so that users can easily and visually see which instance they are in.
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…
When promoting a dataflow from one environment to another, I would like the option to retain the dataflow schedule from the source instance in the destination instance. I would also like the option to execute the dataflow automatically once promoted so that dependent Sandbox jobs downstream do not result in errors because…
As we have versioning to our Sandbox commits, would like to consider the possibility of allowing a checkout of a version that may enable changes to be made without disturbing the actual objects in the instance.
It looks like you're new here. Sign in or register to get started.
Alerts Product Enhancement Ideas
Analyzer Product Enhancement Ideas
API Product Enhancement Ideas
Apps Product Enhancement Ideas
Appstore product enhancement ideas
App Studio Product Enhancement Ideas
Beast Mode Product Enhancement Ideas
Buzz & Navigation Ideas
Charting product enhancement requests
Cloud Amplifier Product Enhancement Ideas
Code Engine Product Enhancement Ideas
Ideas or feedback for the Domo Community or the Community Forums.
Connectors Product Enhancement Ideas
Dashboard Product Enhancement Ideas
Datasets Produce Enhancement Ideas
Domo AI Product Enhancement Ideas
Domo Bricks Product Enhancement Ideas
Domo Developer Product Enhancement Ideas
Domo Everywhere Product Enhancement Ideas
Federated Product Enhancement Ideas
Product enhancement ideas for Domo as a whole
Governance & Security Product Enhancement Ideas
Jupyter Workspaces Product Enhancement Ideas
Localization product enhancement ideas
Magic ETL Product Enhancement Ideas
Mobile Product Enhancement Ideas
Reporting Product Enhancement Ideas
Software integrations product enhancement ideas
SQL Dataflows Product Enhancement Ideas
Variables Product Enhancement Ideas
Workbench Product Enhancement Ideas
Workflows Product Enhancement Ideas
Other Product Enhancement Ideas