Error when loading same table from different Snowflake accounts

[Anonymous]

I'm trying to create a Power BI report to load the same metadata table from two different Snowflake accounts. I have two Snowflake accounts, with different aliases and locators. In both Snowflake accounts, I have a table with the same name and columns, located in the same schema and database in both accounts. However, the number of records and data in each is different.

When I load these two tables into a Power BI report using the Snowflake connector and then refresh the report, the content in both tables is the same. Sometimes it may be from one of the two accounts and sometimes from the other. However, in the "Table" view, you can see that the content in both tables is the same. The query for each table is using a different Snowflake account (and the same warehouse name), but the content in both tables is from one of the two accounts. I've even noticed that when I try to load a new table with the Snowflake connector and enter the Server field for one of the two Snowflake accounts in the browser, it ends up showing me the databases from the other account.

I've also tried loading one of the two tables with a native select * query, and adding an additional field to the select, but the same thing ends up happening.

How can I prevent this behavior?

[v-nmadadi-msft]

Hi @Anonymous 

May I check if this issue has been resolved? If not, Please feel free to contact us if you have any further questions.

Thank you

[Anonymous]

The issue was resolved for me by using the previous versión of the Snowflake connector (version 1.0).

[v-nmadadi-msft]

Hi @Anonymous 

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.

Thank you.

[v-nmadadi-msft]

Hi @Anonymous  ,
Thanks for reaching out to the Microsoft fabric community forum.

Currently, the Snowflake connector implementation 2.0 has the following known issues. There's ongoing work towards a fix 
- Snowflake query with count distinct logic returns incorrect result.

- When creating relationships, encounter error Object reference not set to an instance of an object. The relationship can still be defined once you cancel the pop-up window.
It is possible that may be the cause of the error you are experiencing.

Additionally, it is recommended to upgrade to the Power BI Desktop and on-premises data gateway to the latest version to benefit from the most current capabilities of Snowflake connector implementation 2.0.

I hope this information helps. Please do let us know if you have any further queries.
Thank you

[Anonymous · Accepted solution]

Thanks for your response. If the behavior I'm seeing is a malfunction, I haven't seen it documented anywhere. I'm assuming it must be a malfunction. I'm using the September release of Power BI Desktop. And I was able to work around the issue by using the 1.0 implementation of the Snowflake connector.

[v-nmadadi-msft]

Hi @Anonymous ,
Glad to hear that the issue is resolved using 1.0 implementation. Any issues with implementation 2.0 will be patched in the next release of the Power BI desktop which are inadvertently causing the error.

Thank you

[Anonymous]

Additional information: If I use the 1.0 implementation of the connector 👇, it works fine, the 2 tables appear with different numbers of rows and content in the table view.

[rohit1991]

Hi @Anonymous 

This happens because Power BI sees both Snowflake sources as identical (same schema/table names) and reuses metadata. To fix it, make the connection strings unique in Power Query. In Advanced Editor, define each source separately, for example:

Source_Acc1 = Snowflake.Databases("account1.snowflakecomputing.com", "WAREHOUSE1"),
Source_Acc2 = Snowflake.Databases("account2.snowflakecomputing.com", "WAREHOUSE2")

This way Power BI treats them as two different sources and won’t mix the data.

[Anonymous]

I was using different sources... 

[rohit1991]

Hi @Anonymous 

It looks like both queries still have the same navigation steps and final query names (DIM1_COUNTRY), so Power BI treats them as the same object. Even if accounts are different, the query folding step causes duplication.

Try these fixes:

1. In Advanced Editor, rename each query with a unique step name:

e.g., DIM1_COUNTRY_ACC1 and DIM1_COUNTRY_ACC2.

2. Make sure the Source step explicitly includes the full account URL + DB + Schema.
Example:

Source1 = Snowflake.Databases("account1.snowflakecomputing.com"),
DB1 = Source1{[Name="DB1",Kind="Database"]}[Data],
Table_ACC1 = DB1{[Name="DIM1_COUNTRY",Kind="Table"]}[Data],

Source2 = Snowflake.Databases("account2.snowflakecomputing.com"),
DB2 = Source2{[Name="DB2",Kind="Database"]}[Data],
Table_ACC2 = DB2{[Name="DIM1_COUNTRY",Kind="Table"]}[Data]

3. Load them with different names into the model so they don’t overwrite each other.

This way, Power BI keeps them as separate queries and won’t mix up the data.

[Anonymous]

I tried with this 👇and it didn't work