Recent and slight behavior change in ETL - heads up
NewsomSolutions
Contributor
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
- 1.4K Product Ideas
- 1.4K Ideas Exchange
- 1.4K Connect
- 1.2K Connectors
- 284 Workbench
- 4 Cloud Amplifier
- 4 Federated
- 2.9K Transform
- 88 SQL DataFlows
- 555 Datasets
- 2.2K Magic ETL
- 3.3K Visualize
- 2.3K Charting
- 566 Beast Mode
- 9 App Studio
- 27 Variables
- 577 Automate
- 140 Apps
- 414 APIs & Domo Developer
- 22 Workflows
- 1 DomoAI
- 28 Predict
- 12 Jupyter Workspaces
- 16 R & Python Tiles
- 350 Distribute
- 90 Domo Everywhere
- 258 Scheduled Reports
- 2 Software Integrations
- 91 Manage
- 88 Governance & Security
- 9 Product Release Questions
- Community Forums
- 42 Getting Started
- 28 Community Member Introductions
- 85 Community Announcements
- 4.8K Archive