Forum Discussion

dgwilson's avatar
dgwilson
Icon for Resolver III rankResolver III
1 year ago
Solved

Snowflake Conector 2.0 Preview - January 2025

Asking here if anyone else has had issues testing the new Snowflake Connector in the January 2025 release of Power BI Desktop?

Version: 2.139.1576.0 64-bit (January 2025)
Link to documentation - see the end for the update to the connector
https://learn.microsoft.com/en-us/power-query/connectors/snowflake

I have set the preview function to ON, and have restarted Power BI Desktop.
The documentation says to pickup/use the new connector you inject Implementation="2.0" into the Snowflake.Databases M code.
Source = Snowflake.Databases("contoso.snowflakecomputing.com", "CONTOSO_WH", Implementation="2.0")

I've done this, and in my case I have parameters for the Snowflake Address, Database, and Role
Source = Snowflake.Databases(SF_Address,SF_Warehouse, Implementation="2.0", [Role=SF_Access_Role]),
... it doesn't matter if Implementation is before or after the Role - I get the same error.

I'm getting the following error
Expression.Error: The import Implementation matches no exports. Did you miss a module reference?

Any pointers from the team?





 

  • Answering my own question here... The syntax seems a bit different to the doc.

    [Role=SF_Access_Role, Implementation="2.0"]

    This 
    Source = Snowflake.Databases(SF_Address,SF_Warehouse, Implementation="2.0", [Role=SF_Access_Role]),
    becomes
    Source = Snowflake.Databases(SF_Address,SF_Warehouse, Implementation="2.0", [Role=SF_Access_Role, Implementation="2.0"]),


    It seemed very slow initially to retrieve a simple data set.
    2nd go was quite fast. I'll have to try another table now... there may have been a background install maybe?

     

     

13 Replies

  • dgwilson's avatar
    dgwilson
    Icon for Resolver III rankResolver III

    Answering my own question here... The syntax seems a bit different to the doc.

    [Role=SF_Access_Role, Implementation="2.0"]

    This 
    Source = Snowflake.Databases(SF_Address,SF_Warehouse, Implementation="2.0", [Role=SF_Access_Role]),
    becomes
    Source = Snowflake.Databases(SF_Address,SF_Warehouse, Implementation="2.0", [Role=SF_Access_Role, Implementation="2.0"]),


    It seemed very slow initially to retrieve a simple data set.
    2nd go was quite fast. I'll have to try another table now... there may have been a background install maybe?

     

     

    • dgwilson's avatar
      dgwilson
      Icon for Resolver III rankResolver III

      It wasn't an install.
      Another simple table is taking minutes to load... and that's just the preview.

  • rbriga's avatar
    rbriga
    Icon for Impactful Individual rankImpactful Individual

    I had a major issue with the new Snowflake implementation.

    It works fine in Desktop, but not in Service.

    When using a native Snowflake query, I would get the expected number of rows, but with wrong data.

    ID fields (long text strings) would replicate the same value on other, otherwise correct, rows.

    Note that it's not row duplication. For example, suppose this is the correct query values:

    Product_IDProduct_Name
    aaaaaaaaaaaaaaApple
    bbbbbbbbbbbbBannana
    cccccccccccccccCereals
    ddddddddddddDonut

     The Service refresh would return:

    Product_IDProduct_Name
    aaaaaaaaaaaaaaApple
    bbbbbbbbbbbbBannana
    bbbbbbbbbbbbCereals
    bbbbbbbbbbbb

    Donut

     

    It was hard picking up the reason for this. Removing the Implementation="2.0" tag fixed the issue.

    • AntoineAB1's avatar
      AntoineAB1
      Frequent Visitor

      Hello. I had the same issue and just found out it was coming from the parameter [Implementation="2.0"].

      Any idea how to deactivate this default parameter?

      • dgwilson's avatar
        dgwilson
        Icon for Resolver III rankResolver III

        If you do not want to use the v2 implementation by default - you are best to turn off the preview feature. Then for any given table, you will have to edit the M code in Power Query to remove the [Implementation="2.0"] parameter. That should make Power Query use the v1 connector.

    • dgwilson's avatar
      dgwilson
      Icon for Resolver III rankResolver III

      It's really important that goes as feedback to the Microsoft team. I'm not exactly sure how to do that... I do recall that there may have been a feedback either in Power Query somewhere or on the Web page with the release details. Yea - found it.  https://learn.microsoft.com/en-us/power-query/connectors/snowflake - that's the link to the Snowflake documentation. About half way down it tallks about the new connector and has a link for feedback - https://aka.ms/snowflake-connector-feedback - it's really important you provide this experience and direct feedback to the team.

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi dgwilson ,

     

    Thanks for reaching out.

    I reviewed your post and I think you'v got the answers already.

    Please accept the reply as solution, more people will benefit from it soon.

     

    Best Regards,

    Stephen Tao

  • I tried testing this on a Gen 2 dataflow (rather than Power BI desktop) but it said Adbc isn't available in the current environment.

  • rbriga's avatar
    rbriga
    Icon for Impactful Individual rankImpactful Individual

    The latest updates to the Snowflake 2.0 implementation (February-March 2025) seem to have fixed the duplicates issue.