Don't miss your chance to take the Fabric Data Engineer (DP-700) exam on us!
Learn moreNext up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now
I have two tables.
AzureSQL_Table1
SQLServerLocal_Table1
If I upload my dataset, then to refresh from the service, I need a data source in the data gateway for SQLServerLocal_Table1, but not AzureSQL_Table1.
That's expected behavior.
If I merge in one column fromSQLServerLocal_Table1, onto AzureSQL_Table1, then suddenly the Azure SQL source is asking for an entry in the data gateway.
Is that because the merge will happen on the gateway, not the service, or?
Solved! Go to Solution.
Yes. When you mash up data (merge, append, etc) cloud and on prem data, you need to allow the gateway to access those cloud data sources as shown below from the gateway config in the Power Platform admin panel.
If you are just pulling in the tables directly and not merging, this would not be necessary.
DAX is for Analysis. Power Query is for Data Modeling
Proud to be a Super User!
MCSA: BI ReportingYes. When you mash up data (merge, append, etc) cloud and on prem data, you need to allow the gateway to access those cloud data sources as shown below from the gateway config in the Power Platform admin panel.
If you are just pulling in the tables directly and not merging, this would not be necessary.
DAX is for Analysis. Power Query is for Data Modeling
Proud to be a Super User!
MCSA: BI ReportingIf you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.