Hey there! Let's walk through why you might be hitting a configuration error in Data Studio even when you can access the BigQuery dataset directly. While basic read permissions should work, there are a few often-overlooked checks to make:

Key Permissions & Configurations to Verify #

• Ensure you have bigquery.jobs.create permission: Even if you can read the dataset in BigQuery, Data Studio runs temporary query jobs to pull schema and data. Without this permission (at the project or dataset level), you’ll get a configuration error. This is the most common culprit here.
• Confirm dataset-level (not just table-level) access: If you only have permissions on individual tables within the dataset, Data Studio might fail to connect when selecting the entire dataset—since it needs to read dataset metadata like the list of tables.
• Check for permission sync delays: Google Cloud permissions can take a few minutes to propagate across services. Even if BigQuery shows access immediately, Data Studio might not pick up the update right away. Wait 5-10 minutes and try reconnecting if you recently got access.

Connection Setup Checks #

• Double-check project/dataset names: Google Cloud resource names are case-sensitive. Make sure the project ID and dataset name you enter in Data Studio exactly match what’s in BigQuery (no typos, extra spaces, or incorrect capitalization).
• Verify the connected account: Ensure you’re using the same Google account in Data Studio that you use to access BigQuery. It’s easy to accidentally switch to a secondary account without noticing.

Organizational Restrictions #

If you’re part of a company or enterprise with strict Google Cloud policies, your admin might have set an organization policy that blocks Data Studio from accessing BigQuery. For example, a restrictServiceUsage policy could prevent Data Studio’s API calls to BigQuery. In this case, you’ll need to reach out to your Cloud admin to adjust the policy.

If you’ve gone through all these steps and still run into issues, try creating a simple test report with just one table from the dataset (instead of the full dataset) to narrow down whether the problem is with the dataset itself or a broader permission issue.

内容的提问来源于stack exchange，提问作者Sidharth kaushik