Forum Discussion
Passing Parameter for a PowerBI Report
Hey Anonymous ,
Not sure if this does the trick, but when looking closely at the URL of the failing embedded scenario, I spot two question marks.
Basically, an URL is pointing to a site, but sometimes you can pass parameters and parameter values to the "endpoint" (the website). The website (the endpoint) is processing the parameter(s)/parameter value(s) before returning the result. Sometimes it looks like the website simply opens, most of the it does, but sometimes a lot has happened in the background due to parameter/parameter values.
The structure of the URL looks like this
base urlparameter(s) section
The base url and the parameter section are separated by a questionmark. For the sake of readibility I combined a parameter and its parameter value by an underscore. An url with a single parameter will look similar to the next line:baseurl?parameter_parametervalue
When working with embedded scenarios the base url is:https://app.powerbi.com/reportEmbed
the first parameter is reportid this makes it
https://app.powerbi.com/reportEmbed?reportId=d609fc77-f7af-4153-9796-7e8bcca44f15
If you look closely the next parameter is autoAuth, different parameters are separated by &, the url will then look like the next example:
baseurl?parameter1_parameter1value¶meter2_parameter2valueBe aware that multiple parameters is not the same as passing multiple columns to filter a report. No matter the number of columns there is only one parameter filter.
I think replacing the questionmark (?) right in front of the parameter filter with the & will do the trick.Hopefully, this helps to tackle your challenge.Regards,Tom
Super UserHey Anonymous ,
Not sure if this does the trick, but when looking closely at the URL of the failing embedded scenario, I spot two question marks.
Basically, an URL is pointing to a site, but sometimes you can pass parameters and parameter values to the "endpoint" (the website). The website (the endpoint) is processing the parameter(s)/parameter value(s) before returning the result. Sometimes it looks like the website simply opens, most of the it does, but sometimes a lot has happened in the background due to parameter/parameter values.
The structure of the URL looks like this
base url
parameter(s) section
The base url and the parameter section are separated by a questionmark. For the sake of readibility I combined a parameter and its parameter value by an underscore. An url with a single parameter will look similar to the next line:
baseurl?parameter_parametervalue
When working with embedded scenarios the base url is:
the first parameter is reportid this makes it
If you look closely the next parameter is autoAuth, different parameters are separated by &, the url will then look like the next example:
baseurl?parameter1_parameter1value¶meter2_parameter2value
I think replacing the questionmark (?) right in front of the parameter filter with the & will do the trick.