Closed kevinn1992 closed 4 months ago
@kevinn1992: Hi Kevin, you seem to be right here. There was a explicit choice why we used the Individual one when we created the extension.
At this moment we are actively working on a XPlat version of the task will try to incorporate this stuff into the development.
Perfect! Thanks for the quick response!
@kevinn1992: when you are open to help with testing that would be much appriciated. I'm not a Power BI specialist and created the extension pure out of passion.
Still working on the xplat version. Would be able to incorporate it. Are you maybe able to help testing?
Describe the issue In the Power BI Action Update SQL Credentials there's a scope parameter which has the 2 values "Individual" and "Organization". If I'm not mistaken, this is the privacy level you give to your credentials like 'public', 'organizational' and 'private'. I refer to the official documentation: https://learn.microsoft.com/en-us/rest/api/power-bi/gateways/update-datasource#definitions
When I look at your code for the new Power BI Actions right here: https://github.com/maikvandergaag/msft-extensions/tree/main/azuredevops/powerbiactions-new/powerbiactionsnew/ps_modules/PowerBi for the function 'Update-BasicSQLDataSourceCredentials' (check the image below), it seems that the parameter 'Individual' is not correct.
![image](https://github.com/maikvandergaag/msft-extensions/assets/143867937/d32affcc-1e3c-42f0-9ecc-cc4df98b08ca)
Isn't it the intention to give the 3 different privacy levels: 'public', 'organizational' and 'private' as parameter and change your function to some kind of switch?
Now, no matter what you fill in into your scope the $level variable will always be 'Individual' which is not a privacy level. Please, correct me if I'm wrong.
Kind regards