Direct Query issue with Snowflake

[XCT]

Hi,

Since the last version of PBI desktop, I face a weird issue: I can't connect Snowflake with PBI Desktop in DQ mode.

At the first step of the navigation, I have this message :

I just navigated and didn't make any transformation...

I tried tu use the 1.0 and 2.0 connector, exactly the same result.

Thank you for your support

[Ritaf1983]

Hi @XCT 

This is not related to transformations or to the 1.0 vs 2.0 Snowflake connector.

In DirectQuery mode, Power BI issues metadata queries during the navigation step (before you touch Power Query).
If Snowflake cannot successfully execute those metadata queries, the connection fails immediately.

Typical causes to check:

Missing or invalid Snowflake context

Make sure a Warehouse, Database, and Schema are explicitly available to the user.

The role used by Power BI must have:

USAGE on the warehouse

USAGE on the database and schema

SELECT on the tables/views

This error often appears when Power BI cannot resolve USE DATABASE / USE SCHEMA implicitly.

Role / Warehouse not set explicitly

Try connecting using Advanced options and explicitly specify:

Warehouse

Role

Don’t rely on defaults.

Known issue with recent Power BI Desktop versions

There is a regression where DirectQuery metadata queries fail during navigation even without transformations.

Common workarounds:

Connect via SQL statement (e.g. SELECT * FROM schema.table) instead of browsing

Disable preview features and restart Desktop

Downgrade temporarily to a previous PBI Desktop version if possible

Views with unsupported logic

If you are navigating through views, make sure they don’t contain logic that Snowflake cannot evaluate in metadata queries (e.g. session-dependent logic, non-deterministic functions).

Important point:
The fact that this happens at the navigation step means this is not a Power Query issue, and not something you caused by transformations.

If none of the above helps, this is very likely a Snowflake DirectQuery + recent Desktop bug, and opening a support ticket (with exact Desktop version and Snowflake region) is justified.

If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly

[XCT]

Hi @Ritaf1983 

What I don't understand is that it worked a few weeks ago...

[XCT]

Hi @mohit_sakhare,

Thx for your answer. I will try your workaround.

I thought on 2 other workarounds using Fabric too, for my needs:

1/ Mirroring + Fabric WareHouse + DirectConnexion

2/ Dataflow Gen2 (scheduled every 10min) + Fabric Warehouse + DirectConnexion.

In a second time, I will write a support ticket.

[mohit_sakhare · Accepted solution]

Hi,

You’re not doing anything wrong — this is a known issue/regression with Snowflake in DirectQuery in recent Power BI Desktop versions.

Even if you only click Navigate, Power BI automatically adds a hidden metadata/type-detection step, and that step uses an operation not supported in DirectQuery, which immediately triggers the error. This happens with both Snowflake connector v1.0 and v2.0, and only in DirectQuery (Import works fine).

Workarounds that usually help:

• Use the Snowflake connector Advanced options and provide an explicit SQL statement (for example, SELECT * FROM schema.table) instead of navigating tables.

• Disable Auto-detect column types (File → Options → Data Load), then reconnect.

• As a check, design in Import mode and then switch to DirectQuery.

Bottom line: this is a Power BI Desktop behavior, not a Snowflake or model issue, and it needs a fix from Microsoft.