Forum Discussion
Snowflake Tables Not Merging in Service
Hi etane ,
Adjust the Data Privacy Level of the Snowflake data source to Organizational or Public under Gateway connection settings. moving file of IPs, so then the most dynamic way I’ve found to manage this is with whitelisting the Azure Services Tags in Snowflake. The best place for your vendor to get this list from is Microsoft's public documentation, which can be scripted by them into a process to update a Snowflake Network Policy.
If you are still facing this issue you can rasie ticket for immediate support.
https://go.microsoft.com/fwlink/?linkid=2230908
Hi etane,
Thankyou for the update.
Based on my understanding, the error “On‑Prem execution not supported for entity … since it refers to another entity” occurs when a dataflow mixes cloud sources (for example, Snowflake or Salesforce) with on- premises sources (for example, SQL Server or QAD), or when a deleted on-premises reference still exists in the dataflow. Power Query Online attempts to execute the query in the cloud, but on‑premises sources require an execution path through a gateway, which causes this error. A hidden dependency or computed entity in your dataflow may still reference the on‑premises SQL Server source even after it was deleted. Since on‑premises sources cannot execute in the cloud without a gateway, the refresh fails.
Please follow the steps below which might help to resolve the issue:
- Open the dataflow and remove, or re‑create, any query that is still linked to the deleted QAD/SQL Server table.
- In Manage Connections, delete any unused SQL Server connection and its credentials, then save and refresh.
- If you must include on‑premises SQL tables, connect via an On‑premises Data Gateway and ensure the dataflow maps correctly to that source.
- If the issue persists, recreate the dataflow using only the current sources (Snowflake and Salesforce).
If the error continues, please raise a Microsoft Support ticket using the following link:Microsoft Fabric Support and Status | Microsoft Fabric
Additionally, please refer to the links below:
Merge or append on-premises and cloud data sources - Power BI | Microsoft Learn
Creating a Dataflow - Power BI | Microsoft Learn
On-premises data gateway - Power BI | Microsoft Learn
We hope the information provided will help to resolve the issue. Should you have any further queries, please feel free to contact the Microsoft Fabric community.
Thank you.
Hello.
I have many dataflows that have merged QAD and Salesforce tables without issue for years. So, it shouldn't be a mixing of cloud and on-prem data that is causing the error. The new variable is Snowflake data with on-prem data loaded into the same dataflow even without merge/append and after QAD table and SQL connection is removed from the dataflow. The on-prem source is accessed through a data gateway.
Our IT has created a ticket with MSFT and MINDTREE has been conducting tests with me for the past 2 weeks. We've overcomed merging of Snowflake and Salesforce tables. This current issue is a new variable, and I've requested them to test and waiting for their response.