Mitigating V2 - Federated source limitation in Magic ETL
Hi All,
Not a support question but we are running into an issue and would like to get guidance on how others mitigated this issue. We have a Subscriber instance provisioned to one of our clients, who have created ETLs on top of the sources we had published to that instance. This was in Publish V1. Now with V2, Federated dataset - Domo is not allowing to build any ETLs within or on top of the FDS which pretty much makes it unusable for us. How did you mitigate this limitation? We cannot integrate our entire DB with other client-specific data to a subscriber's instance.
Answers
-
You can use the Dataset Copy connector to copy a dataset from one instance to another. It can be scheduled just like any other connector and would allow your subscribers to build dataflows off of it.
Here are instructions on how to set it up.
https://domohelp.domo.com/hc/en-us/articles/360043436533-DataSet-Copy-DataSet-Connector
**Check out my Domo Tips & Tricks Videos
**Make sure to any users posts that helped you.
**Please mark as accepted the ones who solved your issue.2 -
Thank you @MarkSnodgrass Will take a look.
1
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
- 554 Datasets
- 2.2K Magic ETL
- 3.3K Visualize
- 2.3K Charting
- 561 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