Mitigating V2 - Federated source limitation in Magic ETL
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.