The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
Hi all,
I am looking at parameterizing the PBI dataset to enable deployments from environment to environment (using PBI pipelines), so that I can select the ADLS (storage account) under the "Parameters" section of the dataset for the applicable environment.
I have got a good start, but I am still getting no results back, and some hard to understand errors upon refreshing the dataset.
1. I have created a parameter for ADLS in the dataset. There are 3 entries that have been set (DEV, UAT, PROD)
2. I have created a paramter for "FolderPath" in the dataset. There are 3 entries that have been set (DEV, UAT, PROD)
If I rename the container in UAT incorrectly, I get an error that says it can't find the container.
<snip>
Status code: 404, description: 'The specified container does not exist.'..
</snip>
This means to me that in UAT, PBI is looking at the ADLS account in UAT. If I rename it correctly (matching the dataset), the error changes - meaning it found the container
After I rename and fix the container issue, I see the following error ->
<snip>
</ccon>;The key didn't match any rows in the table.. The exception was raised by the IDbCommand interface. Table:
</snip>
It actually lists the UAT storage in the error too, so it is looking at UAT. Both storage accounts have the same container name and only have 2 csv files. I'm not sure what it is, but I believe I'm missing another paramerter or configuration change.
Solved! Go to Solution.
Hi all,
I was able to get this working after some further troubleshooting. Here are the broken and working steps.
#InError
I was adding the parameter(s) to the step via
Query Editor - Advanced Editor - Manually change the code (replace "string" with param_name)
#working
I removed my manual Mcode updates and used the "cog" on the right for the "source" step. I clicked the "parameter" option and selected the ADLS param I created.
Everything now works on a per environment basis. DEV looks at DEV ADLS, UAT looks at UAT ADLS via the setting of a parameter in the PBI workspace (dataset -> parameters)
Thanks!
Aaron
Hi all,
I was able to get this working after some further troubleshooting. Here are the broken and working steps.
#InError
I was adding the parameter(s) to the step via
Query Editor - Advanced Editor - Manually change the code (replace "string" with param_name)
#working
I removed my manual Mcode updates and used the "cog" on the right for the "source" step. I clicked the "parameter" option and selected the ADLS param I created.
Everything now works on a per environment basis. DEV looks at DEV ADLS, UAT looks at UAT ADLS via the setting of a parameter in the PBI workspace (dataset -> parameters)
Thanks!
Aaron