Issue With Google BiqQuery Connection in Dataflow 2. 'LargeResultDataset' are not valid BigQuery

[DarrenCooper]

Hi,

I'm trying to test ingesting data from Google big query via Datflow Gen 2.

I keep getting the below error at the connection stage , how do I get around it?

An exception occurred: 'LargeResultDataset' are not valid BigQuery options. Valid options are: 'BillingProject, Implementation, UseStorageApi, ConnectionTimeout, CommandTimeout, ProjectId' (Session ID: df892629-e14f-4349-ac6a-c4d98c38e8f3, Region: europe)

I don't have any values set in the LargeResultDataset advanced option.

[Poojara_D12]

Hi @DarrenCooper 

The error you’re seeing — “‘LargeResultDataset’ are not valid BigQuery options” — occurs because Dataflow Gen2 in Microsoft Fabric does not support the LargeResultDataset property, which is a legacy BigQuery connector option used in some older Power Query or on-premises configurations. Even if you haven’t explicitly set that option, it can still appear automatically if your connection or query was originally created in Power BI Desktop, Dataflow Gen1, or another environment where the connector included that property. When you try to reuse that M code or connection string in a Fabric Dataflow Gen2, it fails validation because the Gen2 BigQuery connector only accepts the parameters listed in the error message — namely BillingProject, Implementation, UseStorageApi, ConnectionTimeout, CommandTimeout, and ProjectId.

To resolve this, open your Dataflow Gen2 editor, go to the Advanced Editor, and inspect the M code of your query. Look for any mention of LargeResultDataset (even if it’s null or blank) and remove that parameter entirely from the BigQuery.Database or BigQuery.Contents function. Then save and reconnect using only the supported parameters. If you originally copied the query from Power BI Desktop, recreate the connection natively within Fabric’s dataflow connector interface rather than pasting code, as it will automatically generate a compliant connection string. Once that unsupported property is removed, the BigQuery connection should validate and ingest data successfully.

[v-dineshya]

Hi @DarrenCooper ,

Thank you for reaching out to the Microsoft Community Forum.

The error 'LargeResultDataset' are not valid BigQuery options is due to the Dataflow Gen 2 service passing an unsupported parameter to BigQuery during connection setup.

The 'LargeResultDataset' parameter is not a valid option for BigQuery connections in Dataflow Gen 2. Please refer below the valid options currently supported.

1. BillingProject
2. Implementation
3. UseStorageApi
4. ConnectionTimeout
5. CommandTimeout
6. ProjectId

Note: Even if you haven't explicitly set LargeResultDataset, it seems the system might be injecting it automatically due to a bug or misconfiguration in the underlying Power Query M code.

Please try below steps.

1. Open the Advanced Editor in your Dataflow setup. Check the BigQuery connection line, like below syntax.

GoogleBigQuery.Database([LargeResultDataset = null, ...])

2. Replace above syntax with below syntax.

GoogleBigQuery.Database([
UseStorageApi = null,
ConnectionTimeout = null,
CommandTimeout = null,
BillingProject = "billing-project-id"
])

3. Save and revalidate the connection.

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

Regards,

Dinesh

[v-dineshya]

Hi @DarrenCooper .

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. And, if you have any further query do let us know.

Regards,

Dinesh

[vojtechsima]

@DarrenCooper 
Can you send the M code that is generated on that connection?

It looks like it's putting a random Option to it.