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.8K Product Ideas
- 1.8K Ideas Exchange
- 1.5K Connect
- 1.2K Connectors
- 300 Workbench
- 6 Cloud Amplifier
- 8 Federated
- 2.9K Transform
- 100 SQL DataFlows
- 616 Datasets
- 2.2K Magic ETL
- 3.9K Visualize
- 2.5K Charting
- 738 Beast Mode
- 57 App Studio
- 40 Variables
- 685 Automate
- 176 Apps
- 452 APIs & Domo Developer
- 47 Workflows
- 10 DomoAI
- 36 Predict
- 15 Jupyter Workspaces
- 21 R & Python Tiles
- 394 Distribute
- 113 Domo Everywhere
- 275 Scheduled Reports
- 6 Software Integrations
- 124 Manage
- 121 Governance & Security
- 8 Domo Community Gallery
- 38 Product Releases
- 10 Domo University
- 5.4K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 108 Community Announcements
- 4.8K Archive