Magic ETL Product Enhancement Ideas
I think a good option would be that if a column name is changed in the Column select tile that if that old column is being used in beastmodes that we can push that change to all affected beastmodes. When managing 100's or thousands of beastmodes it makes it difficult to go back and correct if we have to change a column…
Ability to select and move multiple columns at once and reorder them. Today we can select and move only one field at a time.
Have a one click solution for ordering fields alphabetically in the ETL - Select Columns utility
I would love to be able to create an ETL and save that to use in other flows. A "save as template" button would be amazing. It would only save the tiles, not the columns, so you wouldn't have to delete everything before you start. We use recursive dataflows a lot, so it would be amazing if I could save that flow, and then…
We all have ETLs where we use common logic over and over again. I propose an idea to enhance MagicETL with something called 'Recipes'. A user could create a new recipe within Magic, add a series of tiles into it that do some common logical steps and save it with a given name (e.g.. 'Strip Whitespace and Split String'. Once…
Hi Domo, It would be very helpful if we could have ETLs trigger differently based on if the component datasets were updated manually or automatically. Example: If a dataset is automatically updated, then the subsequent ETL triggers should work just fine. However, if one dataset needs to be manually updated, it will not…
Apologies if this has been requested in the past. I would like a case insensitivity checkbox on the join tile. In the example below, I have created two datasets. In dataset2, I have a list of words in varying cases: lower, upper, and proper. If I join the datasets, I get different results based whether the words in…
Is there a way to annotate part of an ETL dataflow like the following
When Magic ETL becomes complicated, should we have a feature that suggests and organizes features into mini ETLs for the data sources? These mini ETLs could then expand into a larger window within the main ETL. This would allow us to minimize it later and continue the process without needing to create multiple output ETLs…
We have really appreciated all the quality-of-life updates to Magic ETL over the past few months! I have a few ideas to improve a pain point we frequently encounter when building ETL's. Some of our standard schema is verbose and requires field name prefixes when ingesting from certain systems. When we attempt to alter…
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