Forum Discussion
Change Source for Azure Data Bricks within Power BI Desktop
Hi,
I am currently pulling data into Power BI from my Azure Data Bricks Cluster using the Azure DataBricks connector from the Power BI Desktop.
However I can't seem to paramertise the connection. The Change Source... option is always greyed out. I am just checking if this is a known limitation or if there is anyway around this as deploying reports through environments is very cumbersome as we have to manually update the connection string for every report for every environment.
Thanks for your help!
5 Replies
- AnonymousNot applicable
Hi jack_kennedy ,
We can use the created parameters to get data. In Power query, we can get different data from different data sources by changing the current value
For details, you can check the relevant content in the following link:https://powerbi.microsoft.com/en-us/blog/deep-dive-into-query-parameters-and-power-bi-templates/
https://community.powerbi.com/t5/Desktop/Changing-Data-Source/td-p/497753
https://github.com/Microsoft/DataConnectors/issues/69
Best Regards,
Liu Yang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
- jack_kennedyFrequent Visitor
Hi,
High. Thanks for taking the time to reply - however I still cannot get this to work. I have set up a Parameter called ADBConnection and set its value to "adb-XXXXXXXXXXXXXX.XX.azuredatabricks.net", "sql/protocolv1/o/XXXXXXXXXXXXX/XXXXXX-XXXXXXXXX-XXXXXX"
Then in Power Query I have the following to set the connection string:
let
Source = Databricks.Contents(ADBConnection, [Database=null, BatchSize=null]),However I keep getting the error below:
Any help appreciated. Thanks!
- AnonymousNot applicable
Was this issue resolved? I am facing the same issue. However with personal access token it seemed to work but we cant use access tokens always
- power_user_123Frequent Visitor
I am facing the same issue too. How did it work with personal access token ?
- Don-BotHelper V
It looks like this is still an issue. However, I got around it by simply inserting my parameters into the M Code myself. I created parameters (with text) like you normally would. Then in the M Code in edit query I replaced the current httppath and source with my parameters