Snowflake Connector 2.0 - not recognising boolean data in native queries

[reubwork]

Since the May release, any native query using a Snowflake Connector v2.0 connection without an explicit data type casting experiences data errors on refresh

let
    Source = Snowflake.Databases("<snowflake account url>","<warehouse name>",[Implementation="2.0"]),
    data = Value.NativeQuery(
                Source{[Name = "<database name>",Kind="Database"]}[Data],
                "select false as v union all select true as v"
                , null
                , [EnableFolding = true]
            )
in
    data

Workaround is to ensure the datatype is explicitly assigned in power query, but this will break all reports that haven't already had this done. 

[reubwork · Accepted solution]

Raised as an issue. 

https://community.fabric.microsoft.com/t5/Issues/May-25-update-for-Snowflake-Connector-v2-has-broken...

[v-pgoloju]

Hi @reubwork,

Thank you for reaching out to the Microsoft Fabric Forum Community.

If the issue still persists, I’d recommend posting it in the Issues forum. This allows the Microsoft support team to review it more closely and provide deeper, environment-specific assistance.

https://community.fabric.microsoft.com/t5/Issues/idb-p/Issues

If this solution helped, please consider marking the response as accepted and giving it a thumbs-up so others can benefit as well.

Best regards,
Prasanna Kumar

[v-pgoloju]

Hi @reubwork,

Just following up to see if the solution provided was helpful in resolving your issue. Please feel free to let us know if you need any further assistance.

If the response addressed your query, kindly mark it as Accepted Solution and click Yes if you found it helpful  this will benefit others in the community as well.

Best regards,

Prasanna Kumar

[reubwork]

No, it's not resolved.

I'm pretty sure this is a bug. 

[reubwork]

Hi Rohit,

Yes, I said in my post that is the workaround. 

As far as I can tell this is an as yet undocumented breaking change. 

Given that the V2 connector is now enabled by default... I don't think this is acceptable as a solution.

[rohit1991]

Hi @reubwork ,

Since v2 of the connector rolled out, Power BI doesn’t always recognize boolean (true/false) columns correctly from native SQL queries. Instead, you’ll get data type errors or mismatches, and sometimes reports that worked before will suddenly fail, especially if you’re not explicitly casting types in Power Query.

Here’s what you can do right now:

1. Workaround: In Power Query, right after you load your data, go to the boolean column, and manually set its type to “True/False” (Boolean). If you’re still getting errors, sometimes it helps to CAST your boolean as an INT or STRING in your SQL, then convert it to Boolean in Power Query.
   
   

2. No permanent fix (yet): Unfortunately, there isn’t a true fix right now, unless your org can somehow use the old connector version, but for most of us, v2 is enabled by default and can’t be rolled back.

[reubwork]

Additionally... forcing the type conversion doesn't actually work, as it treats the snowflake value TRUE as a boolean false. 

[reubwork]

[reubwork]

Error presented