Forum Discussion
QuickBooks Connection not available in pipeline CopyData Source
When I set up the connection in Manage Connections and Gateways, it gives me a disclaimer that it is "not supported by Dataflows, Dataflows Gen2, and Datamarts." If it is not supported by the CopyData activity of a pipeline eiter, THAT should be mentioned there as well:
I have created a solution in classic Azure Data Factory, which has a native (albeit in preview, and still preview after like 8 years) connector for QBO. The trouble there is that the Refresh Token only lasts about 24 hours. We are working on a process to renew that Refresh Token programatically and store it in an Azure Key Vault, which the ADF Linked Service can utilize to make the connection.
Fabric Dataflows (Gen 1 or Gen 2) do not support external interactions with parameters. So if I built this using Dataflows, the Refresh Token would need to be manually edited and saved every DAY. NOT sustainable.
So I'm back to paying for architecture OUTSIDE of Fabric just to get raw data INTO Fabric. I put in a Fabric Ideas item to allow the QBO connection broader adoption, but I'm not holding my breath.
When I set up the connection in Manage Connections and Gateways, it gives me a disclaimer that it is "not supported by Dataflows, Dataflows Gen2, and Datamarts." If it is not supported by the CopyData activity of a pipeline eiter, THAT should be mentioned there as well:
I have created a solution in classic Azure Data Factory, which has a native (albeit in preview, and still preview after like 8 years) connector for QBO. The trouble there is that the Refresh Token only lasts about 24 hours. We are working on a process to renew that Refresh Token programatically and store it in an Azure Key Vault, which the ADF Linked Service can utilize to make the connection.
Fabric Dataflows (Gen 1 or Gen 2) do not support external interactions with parameters. So if I built this using Dataflows, the Refresh Token would need to be manually edited and saved every DAY. NOT sustainable.
So I'm back to paying for architecture OUTSIDE of Fabric just to get raw data INTO Fabric. I put in a Fabric Ideas item to allow the QBO connection broader adoption, but I'm not holding my breath.
Hi ToddChitt , We are sorry for the inconvinience caused by the disclaimer and other fabric features. Your ADF workaround with Azure Key Vault for token renewal is a smart solution given Fabric’s current constraints, especially since Dataflows lack external parameter support. Your Fabric Ideas submission could drive future improvements, we thank you for that.