Recent and slight behavior change in ETL - heads up

NewsomSolutions
Domo Employee
in Magic ETL
This may have been mentioned already and I have missed it, but if you do recursive dataflows or any dataflow in Magic ETL where you are bringing in the output as the input...in the past the 2nd iteration of that dataset would get the 1 appended to it at the end of the name. Now the reverse occurs and the original get the 1 appended to it and the new version does not. I thought the first few times I saw this last week that it was me, but I recorded myself and it is definitely a change in behavior. Just a heads up if you see some outputs that have a 1 appended to it and you weren't expecting it after building a ETL dataflow.
Matt
2
Categories
- All Categories
- 2K Product Ideas
- 2K Ideas Exchange
- 1.6K Connect
- 1.3K Connectors
- 311 Workbench
- 6 Cloud Amplifier
- 9 Federated
- 3.8K Transform
- 660 Datasets
- 117 SQL DataFlows
- 2.2K Magic ETL
- 816 Beast Mode
- 3.3K Visualize
- 2.5K Charting
- 84 App Studio
- 46 Variables
- 778 Automate
- 190 Apps
- 482 APIs & Domo Developer
- 83 Workflows
- 23 Code Engine
- 41 AI and Machine Learning
- 20 AI Chat
- 1 AI Playground
- 2 AI Projects and Models
- 18 Jupyter Workspaces
- 412 Distribute
- 120 Domo Everywhere
- 281 Scheduled Reports
- 11 Software Integrations
- 145 Manage
- 141 Governance & Security
- 8 Domo Community Gallery
- 48 Product Releases
- 12 Domo University
- 5.4K Community Forums
- 41 Getting Started
- 31 Community Member Introductions
- 115 Community Announcements
- 4.8K Archive