What is happening?
When clicking the "Create dashboard" button in Alvie, Looker Studio fails to load the template or generate the report. Instead, it displays a technical error stating it cannot read the specific table.
Error: An error occurred while building your report: Unable to read the table 'project-id/dataset/table_id'.
Why did this happen? This error typically occurs due to an account mismatch in your browser. Common causes include:
Incorrect Google Session: You are logged into multiple Google accounts, and Looker Studio is attempting to build the report using an email address that does not have access to the BigQuery data.
Lack of BigQuery Permissions: The active Google account in your current browser tab lacks the BigQuery Data Viewer or BigQuery Job User roles for the project mentioned in the error message.
Authentication Timing: The Alvie session is using one email, but the redirect to Looker Studio defaults to your "Primary" Google account, which may be a personal or unrelated work email.
Solution Follow these steps to resolve the issue:
Identify the Required Account: Note the project-id mentioned in the error message. This corresponds to the Google Cloud project in your Alvie configuration.
Switch Browser Profiles or Accounts: * The Copy/Paste Method: Copy the entire URL from the address bar where the error is appearing. Open a new "Incognito" window or a different browser profile where you are logged in only with the email that has access to the BigQuery project. Paste the link there.
The Sign-in Method: Ensure you are signed in to the correct Google account before clicking Create dashboard in Alvie.
Action: Once logged into the correct account, the redirect link will successfully authorize the data and allow you to save a copy of the template.
External Steps: If you are unsure which account has access, check the Setup → Data sources tab in Alvie to see which Google Cloud credentials were used for that specific project.
Verify: Once the dashboard loads with your data, click Save and share in Looker Studio. The status in Alvie will effectively be Healthy.
Prevention & Tips To avoid seeing this error again:
Use Dedicated Chrome Profiles: Keep your "Alvie/Work" Google account in a separate browser profile to prevent account "bleeding" when redirected to Looker Studio.
Verify IAM Roles: Ensure the email you use for reporting has permanent access to the BigQuery project.
If you encounter any further issues or need additional assistance, please don't hesitate to reach out to the Alvie support team.