I got the read access on a dataset in bug query. However when I try to connect it in data studio. I get a configuration error.
Tried reconnecting the dataset and even though i can access the dataset if i login in BigQuery.
Any ideas, if I need any special permissions to connect that dataset to from datastudio?
If you get configuration error on any shared dataset make sure you have Viewer Permission. BigQuery Viewer Permission will not work for this.
Related
I am using Dataform to create a table on a dataset that I have created on a Google Cloud project, but I get this error:
"Access Denied: BigQuery BigQuery: Permission denied while getting Drive credentials."
Why? What should I do about this?
In a compiled version of a sqlx dataform file I try to create or replace a table.
CREATE OR REPLACE TABLE my_project_id.my_data_set.my_table
I'm not using a table that reads something from Google Drive but I am creating a new one. The service account associated with my dataform project has Dataset Owner access rights to my_data_set, and interestingly the dataform project is able to create views, but not tables.
I finally found a solution to this problem. To solve this problem one has to do this:
Check all the source tables that the dataform project has.
If any of the source tables is based on a Google Drive data, such as Google Sheet, give the service account associated with the dataform project view access to it.
Interestingly, dataform is not able to create table if it does not have access rights to the source of the tables that it reads.
I am trying to connect to AWS Athena from Power BI using the new Athena connector. The first page prompts for a DSN which I supply (and which works when connecting through the old ODBC method) but when the new connector attempts to connect with this DSN the following error is thrown:
Unable to connect
We encountered an error while trying to connect. Details: "We cannot
convert the value null to type Record."
I had the same issue and I figured out the reason it was happening. When you mention your DSN in the Amazon Athena (Beta), the next thing it will ask is your login (which has two options).Do not take the 2nd option. Pick the first option where the all setting are pulled from your DSN settings, which you did to setup your datasource.
Now if you once did it wrong, It won't ask you again the same things to fix it. Create a new powerbi file and do the steps.
As Janzaib mentioned above, you picked the wrong option when you set up your datasource. But you don't need to create a new file. You can click Data source settings and then find the name of the DSN and edit the permissions. Then the setting is pulled from your DSN and you are good to go.
I had to do a strange workaround to get this to work for me. When I selected the Amazon Athena connection type in PowerBI, typed in the DSN name, and hit OK, I got the error above with no way to correct it. To get it to work, I typed a dummy name in the Role entry ("xyz") before hitting OK. Then I was presented with an authentication dialog - where I could select "Use Data Source Configuration," which would work.
I have made a Power BI Dashboard with Analysis Services (Live Connection). I have full access to the database and in Power Bi Desktop everything works (all data is visible and updated).
Then, when I publish the dashboard, and go to app.powerbi.com to open the DB, it gives me the error message that it cannot access the data source. "This report could not access its data source. please contact , the author, to have it fixed." However, the gateway is set correctly and also connected to the corresponding dataset. I've already delete and re-create the role in the database. What is noticeable is that the update date right after the publishing says: 1.1.53, 00:53:28. After the first gateway update it shows the correct date and time. Can anyone help me to fix the problem? Thank you very much!
You need to assign all of the end users read/write roles on the Tabular model.
I created a BigQuery table from Google Sheet.
When I am trying to query this table from BigQuery - everything is ok.
In the Data Studio, I've created a data source that calls that BigQuery Table, but when I'm attempting to use this data source in a report - I get an error.
Then I checked the Query history in BigQuery to see how Data Studio tries to access it, I saw this error message:
Error while reading table: dataset.Table_sheet, error message: Failed
to read the spreadsheet. Error code: PERMISSION_DENIED
The same query when I run it directly in BigQuery works just fine, but not when I access it from Data Studio.
The solution to the problem - surprised me =).
Dear stranger, you should go to the data studio and create a data source directly from the Google Spreadsheets - you will be prompted to authorize Data Studio to access your Google Drive. After granting access to this new data source - the one you created before will be able to query the table as expected. Seems like a workaround, but it works.
I have a report from power bi, which has a direct connection to the server to obtain the data (analisys services). To access the data from my account I use the on premises data gateway, which works correctly and I can view the data in the web app. The problem appears when the report to another user (both having the pro account). From the account of the other user you can see that a report was shared, but when you open it the following error appears: "Error executing the query because the cube or some internal structures have not been processed (or do not exist)" .Also grant owner permissions to the cube to the user in question. Any clue where it might be failing?
I think you should Map usernames for this connection.
Go to settings -> Manage gateways
Under your gateway cluster you should have your data source (if not you can add a new one and it's quite straight forward to set up, just choose analysis services, write in database name of server and credentials) and then you should go to Users tab.
There you can see Map usernames where you need to Replace the account to which you want to share with an account that has permissions in SSMS.
For example you want to share to example#elpmaxe.com and you have granted permissions in SSMS to user named example.elpmaxe, so in map usernames you would replace example#elpmaxe.com with example.elpmaxe
The answer was easy but finding it was difficult. The issue was that even though you had assigned the role in the cube to the user who wanted to share the report, you had not given them read permission (assuming the role had already been assigned). It is a basic problem but if you are a beginner in analysis services it can get complicated.