We are migrating our Report Server to Report Server Power BI and we have a lot of rdl reports to migrate.
We have 1 rdl report that has a lot of url links to other reports on the report server that get built up with specific parameters via values in the RDL file.These work absolutely fine on SSRS 2012 and they are built up and look like;
https://xxxxx.xxxxx.com/ReportServer/Pages/ReportViewer.aspx?/Production/Customer%20Performance/Deliveries&rs:Command=Render&Company=2218&DIETSwitch=1&StartDate=2018-06-30%2022:00:00&EndDate=2018-07-11%2022:00:00&SearchValue=&TotalDeliveries=1&OnTime=1
I use variables in the rdl as part of building these and the root of this is;
="https://xxxxx.xxxxx.com/ReportServer?/Production/Customer Performance/"
I then use other variables to specify specific reports in that folder and concatenate them together.
However on our new SSRS Power BI it doesn't render the url in the same way when the report is run and I get an error;
The full path must be less than 260 characters long; other restrictions apply. If the report server is in native mode, the path must start with slash. (rsInvalidItemPath)
The url doesn't look the same and is missing the ReportViewer.aspx? section on the SSRS Power BI version.
Even when I try to build the url manually including the ReportViewer.aspx? it just returns blank and doesn't open the report.
Is it still possible to build URL's in reporting services files built up with values that you can pass as parameters in the URL on SSRS Power BI? I suspect I may have to build them in a different way.