PowerBI with Snowflake released refresh error: 'Implementation' are not valid Snowflake options.

[SteveShen]

PBI Version: 2.149.1252.0 64-bit (November 2025)

After I imported table from Snowflake, in PowerQuery source, there will show a param named Implementation="2.0"

Then refresh in PBI Desktop succeeded, but after I release it to PBI server, it shows error while refreshing: 

'Implementation' are not valid Snowflake options. Valid options are: 'ConnectionTimeout, CommandTimeout, CreateNavigationProperties, Role'

Complete Error msg:

Data source error:

{"error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","pbi.error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","parameters":{},"details":[{"code":"DM_ErrorDetailNameCode_UnderlyingErrorCode","detail":{"type":1,"value":"-2147467259"}},{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"'Implementation' are not valid Snowflake options. Valid options are: 'ConnectionTimeout, CommandTimeout, CreateNavigationProperties, Role'"}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.ValueError.Reason","detail":{"type":1,"value":"Expression.Error"}}],"exceptionCulprit":1}}}

[chiragdb2026]

This error is almost always caused by a version mismatch between Power BI Desktop and the On‑Premises Data Gateway.
- Desktop (Nov 2025 v2.149): Introduced the new Snowflake connector with Implementation="2.0" (Arrow‑based).
- Gateway: If it’s on an older build, it doesn’t recognize that parameter and throws the “valid options” error you’re seeing.
Fixes:
- Update the Gateway → Recommended. Install the latest Gateway so it matches your Desktop version; the refresh will succeed.
- Quick workaround → Edit the M code in Power Query and remove [Implementation="2.0"]. The connector will fall back to the legacy implementation, which the older Gateway supports.
In short, either align Gateway and Desktop versions, or strip out the Implementation flag until your Gateway is updated.

[v-karpurapud]

Hi @SteveShen 

Thank you for reaching out to the Microsoft Fabric community forum.

I would also like to thank you  @burakkaragoz for your active participation and for sharing solutions within the community forum. 

I hope the information provided helps resolve your issue. If you have any further questions or need additional assistance, please feel free to contact us. We are always here to help.

Best regards,
Community Support Team

[burakkaragoz · Accepted solution]

Hi @SteveShen ,

This is a classic version mismatch between your Power BI Desktop and your On-Premises Data Gateway.

Here is exactly what is happening:

• Your Desktop: You are on the November 2025 release (v2.149). This version introduced a newer Snowflake connector (Implementation 2.0) likely for better performance using Apache Arrow.

• Your Gateway: The Gateway installed on the server is likely an older version that does not yet recognize the Implementation="2.0" parameter. That is why it lists the "Valid options" and Implementation is missing from that list.

How to fix it:

Option 1: Update the Gateway (Recommended) Ask your IT or Admin team to update the On-Premises Data Gateway to the November 2025 (or latest) version. Once the Gateway matches your Desktop version, it will understand what "Implementation 2.0" means.

Option 2: The Quick Workaround (Edit M Code) If you cannot update the Gateway immediately, you can force the report to use the legacy connector:

1. Open Power Query Editor.

2. Select your Snowflake query and open the Advanced Editor.

3. Locate the part Snowflake.Databases("...", "...", [Implementation="2.0"]).

4. Simply remove the [Implementation="2.0"] part so it looks like Snowflake.Databases("...", "...") or just Snowflake.Databases("...", "...", []).

5. Publish the report again.

The Gateway should accept the request since it defaults to the old implementation.

Hope this gets your refresh working again!

---

If my response resolved your query, kindly mark it as the Accepted Solution to assist others. Additionally, I would be grateful for a 'Kudos' if you found my response helpful.
This response was assisted by AI for translation and formatting purposes.

[RDM-Analytics]

Hey @burakkaragoz , I ran into this issue as well and removed the Implementation 2.0 parameter as my IT dept is very restricted and could be a long time before they update the gateway. This worked for allowing the refresh to continue but it looks like columns of DATETIME format are now broken. Have you seen this issue before?

[SteveShen]

Hi @burakkaragoz 

Thanks for advice!

I'll ask for our IT admin to try the gateway update.