Is there a limit to the number of inputs on a Magic ETL dataflow?
Comments
-
To my knowledge, there isn't a cap, however I've never gone beyond 5 inputs.
I'm not familiar with your data landscape but taking a step back, it might be prudent to consider other ETL options given your estimation of inputs. That dataflow would be cumbersome at best to manage and make changes to, not to mention debug for errors and even fully execute.
If possible, I'd recommend trying to do some of the heavy lifting on-premise maybe in SQL environment.
0 -
Can you provide some more info about your use case? I agree with the other post, it seems like you may be better off doing things somewhere else to bring into Domo
**Make sure to like any users posts that helped you and accept the ones who solved your issue.**0 -
Agreed with responses above. Even if you can I'd have to question if that's something you want to maintain. Maybe if you let us know about why you have 100 sources to begin with. There may be solutions to pre-combine that data before loading into Domo.
Aaron
MajorDomo @ Merit Medical
**Say "Thanks" by clicking the heart in the post that helped you.
**Please mark the post that solves your problem by clicking on "Accept as Solution"0
Categories
- 10.6K All Categories
- 8 Connect
- 918 Connectors
- 250 Workbench
- 477 Transform
- 1.8K Magic ETL
- 69 SQL DataFlows
- 478 Datasets
- 218 Visualize
- 260 Beast Mode
- 2.1K Charting
- 12 Variables
- 19 Automate
- 356 APIs & Domo Developer
- 89 Apps
- 3 Workflows
- 20 Predict
- 5 Jupyter Workspaces
- 15 R & Python Tiles
- 249 Distribute
- 65 Domo Everywhere
- 243 Scheduled Reports
- 21 Manage
- 42 Governance & Security
- 191 Product Ideas
- 1.2K Ideas Exchange
- 11 Community Forums
- 27 Getting Started
- 14 Community Member Introductions
- 55 Community News
- 4.5K Archive