-
Cloud Amplifier - Snowflake - Choose schema and custom DB and Schema names
For Cloud Amplifier on Snowflake, it would be helpful if we were able to: Choose both the destination DB and Schema that the data lands in (rather than having to go only to the Domo managed DB and Domo manage schema "RAW_DOMO". Be able to rename the DB and Schema that is generated when the connection is set up The reason…
-
Allow sorting of dashboards in menu
It would be helpful to allow sorting/grouping of dashboards in the left burger menu bar. For example, being able to put all dashboards related to 'sales' in a 'sales' folder or to allow them to have a different colour in the menu.
-
Rotation of Domo app on iPhones
It is not currently possible to rotate a dashboard on the Domo app on an iPhone. This can be done on Android devices. It would be helpful if we could also rotate on iPhones to make dashboards easier to view.
-
Allow naming of tables in Snowflake with Cloud Amplifier
Currently when data is added into Snowflake via Domo's cloud amplifier, it is not possible to choose the name of the dataset in Snowflake. It is named as 'DATASET_0001' etc. but it would be better to be given the same name as the dataset in Domo.
-
Limit options in page filters
I do not need all the fields from the dataset or all the BEAST MODES created to be available for the end-user, as they might get confused with the hundreds of fields available in the drop-down. I want to restrict the fields that I want to show to the customer on the page level based upon the business. I might use many…
-
Estimate processing time of each step in Magic ETL v2
When creating any ETL the user interface is unable to alert you the impact of the change will make on the dataflow. If I create a transformation that is not optimized I should be alerted this will increase process time. It would be helpful to have a time estimation in Magic ETL itself as to how long each step will take…
-
Add dates to Excel when exporting underlying data from a card
When data get extracted from users across the dashboards the export file only has the content but no meta information (dataset, time of export, filters applied, person who exported). So when distributing or asked to update it's not always clear where the data come from. It would be useful to add this information to the…
-
Colour palettes
Colour palettes are not available in each card requiring a substantial effort to apply a consistent look and feel using default colours. For example, when using the same dataset, it would be helpful to have cards automatically use one colour palette for one brand, and another colour palette for another brand.
