topic Set AzureBlob Datasource key using REST API in Developer

Set AzureBlob Datasource key using REST API

Anonymous — Thu, 30 Jan 2020 00:27:01 GMT

Hi,

I have a report which I embedded to my application using pbie.

the report itself have been embedded successfully, but the dataset cannot be refreshed.

after some checking, I know that the dataset doesn't have enough credentials to access my datasource, which are a csv file in Azure Blob storage.

Now, if I manually add my azure blob credentials to my datasets from power bi workspace it could be refreshed.

But, I want to automatically set my credentials from my application which are written in javascript.

I tried to use this API first to get my gateway and Datasource ID

GET https://api.powerbi.com/v1.0/myorg/datasets/{datasetId}/datasources

it went well and I got the information perfectly.

next step, I wanted to update my datasource credentials information using this API

PATCH https://api.powerbi.com/v1.0/myorg/gateways/{gatewayId}/datasources/{datasourceId}

with my OAuth token as my Authentication header, and request body like below:

{ "credentialDetails": { "credentialType": "Key", "credentials": "{\"credentialData\":[{\"name\":\"key\", \"value\":\"MY KEY\"}]}", "encryptedConnection": "Encrypted", "encryptionAlgorithm": "None", "privacyLevel": "None" } }

but it gave my 401 error with response :

{ "error": { "code": "PowerBINotAuthorizedException", "pbi.error": { "code": "PowerBINotAuthorizedException", "parameters": {}, "details": [], "exceptionCulprit": 1 } } }

can anybody give me a hint for where I done wrong?

or maybe if there are any other way to do this I would appriciate the infromation

bests,

Re: Set AzureBlob Datasource key using REST API

duartte23 — Fri, 21 Aug 2020 18:12:03 GMT

Hi,

Did you get an answer to this issue?

Re: Set AzureBlob Datasource key using REST API

asarraf21 — Thu, 26 Jan 2023 18:45:10 GMT

I am having the same issue, it is reported elsewhere too.

I think the core of the issue is that the PATCH endpoint does not work. My usecase was a BASIC user/pass to update datasource for Azure SQL server and it is throwing the same exception. This is my payload:

{ "credentialDetails": { "credentialType": "Basic", "credentials": "{\"credentialData\":[{\"name\":\"username\", \"value\":\"admin\"},{\"name\":\"password\", \"value\":\"S3cretPasswrd\"}]}", "encryptedConnection": "Encrypted", "encryptionAlgorithm": "None", "privacyLevel": "Private" } }

The challenge is the exact same payload and endpoint works fine when you are logged in and run it interactively in the REST page. But when you get the token all through the REST api it throws an exception.