Magic ETL Product Enhancement Ideas
Hello, It would be helpful if we had the option to add items to the Magic ETL Checklist. This would allow for each organization to be able to make sure everyone is designing their ETLs per their procedure/guidelines. For example, if we are requiring the designers to 'label' all tiles, then we could add a checklist item;…
Currently when you view the run details of a MagicETL dataflow, we can see the rows processed, duration, and status of each action in the ETL canvas. It would be very helpful to see an additional column that shows the number of output rows of each step, similar to how we can see the output of each transform in MySQL…
The functionality I require is already available in the MySQL and Redshift DataFlow… …in this example deselecting "department" and "state" columns. This option would make it possible not to load all columns for all rows in the DataSet. I hope it will be available in the Magic ETL input DataSets as soon as possible. Thank…
Troubleshooting would be improved by the ability to click on the header of a preview column to see all distinct values in the column, similar to tables in Excel.
It would be helpful in an ETL to be able to search for a field name and have the tiles that directly reference that field name be highlighted. Many times when supporting dataflow development we are looking for a field and we have to open every tile to see where that field is referenced - in join, in formulas, in filters,…
Appends should default to "Include All Rows" and not change every time inputs are added/removed. Huge quality of life upgrade!
This would be a small change that could help organize extremely busy dataflows. While you can currently change the color of the line
Currently, a user can see either the configuration of an ETL tile OR they can tab over to the notes section. It would be nice to see both views at once when writing notes on the configuration or editing the configuration based on the existing notes.
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.
I am pulling DomoStats data sets for: DataFlow Input DataSets DataFlow Output DataSets First Step - Combining input_output defined as: Select dfin."Dataflow ID" as dfid , dfin."Datasource Input ID" as dsin , dfout."Datasource Output ID" as dsout from "dataflow_input_datasets" as dfin join "dataflow_output_datasets" as…
It looks like you're new here. Sign in or register to get started.
Have a Domo product enhancement idea? Submit or upvote on ideas in the Ideas Exchange.
Ask questions about Connectors, Workbench, Cloud Amplifier and get best practices from Domo peers
Ask questions about Magic ETL, SQL DataFlows, DataFusion, Dataset Views and get best practices from Domo peers
Ask questions about Beast Mode, Cards, Charting, Dashboards, Stories, Variables and get best practices from Domo peers
Ask questions about App Framework, Workflows, Domo Bricks, Domo Developer, API and get best practices from Domo peers
Ask questions about Jupyter Workspaces, R & Python Tiles, AutoML and get best practices from Domo peers
Ask questions about Domo Everywhere, Scheduled Reports, Mobile and get best practices from Domo peers
Ask questions about Governance Administration, Approvals, Teams, Alerts, and Buzz and get best practices from Domo peers
Watch how our Customers are using Domo to solve their complex problems.
Domo support and product teams are here to live-answer questions about the most recent product releases. Please post questions in this Forum board for all users to benefit (rather than submitting a support ticket).
Questions or discussions related to Domo University, trainings and certifications