Please Vote on Microsoft Connect Items

I’ve posted two feedback items on the Microsoft Connect today, suggesting feature enhancements to Power View and Reporting Services.  If you think these capabilities would be important, I encourage you to follow the links below to the Microsoft Connect site and vote on these items.

Power View reports can be published to SharePoint in a couple of different ways with some inconsistent behavior

https://connect.microsoft.com/SQLServer/feedback/details/779456/publish-or-save-rdlx-from-xlsx-files

Publish or save RDLX from XLSX files

In order to give user a consistent experience in SharePoint, we need to be able to publish Power View reports as separate documents if they were authored in Excel. As it stands, a PowerPivot model can be published and then Power View reports are created separately. Each reports has multiple views that can be exported as a single PowerPoint presentation.
If a user were to author a PowerPivot model and Power View reports using the respective Excel 2013 add-ins, and then publish that xlsx document to SharePoint, consumers will have a different experience all together. This is inconsistent and confusing.  If the reports could be saved from Excel as separate RDLX files, they could then be published separately.

I suggest the following capabilities:

– Save RDLX files from Excel 2013 to separate files
– Save all Power View reports in an XLSX to a different views in a single RDLX file
– Extract the RLDX content during publishing and deploy it as a single Power View report with multiple views.

 

Reporting Services URL string limit:

Reporting Services has a URL command limitation that vary a little because of the URL limits of browsers and web servers.  In most cases, the limit is 260 characters which doesn’t give you much opportunity to pass in multiple parameter values.  This is especially true for multi-value report parameters.  Internally, SSRS uses stored parameters to pass values for report actions.    When a report action is used, all of the parameter values are actually written to the report server content database and an ID is used to pass the request token to the target report.  If we could utilize that same mechanism for URL actions, we could work-around this limitation.

https://connect.microsoft.com/SQLServer/feedback/details/779454/use-stored-parameters-to-work-around-url-size-limit

Use stored parameters to work-around URL size limit.

Per feedback item #752496 (which has received no response), please enable to ability to set stored parameters for a report execution to allow a report to run with a URL request. There are several common scenarios (such as working around the lack of a linked report feature in SharePoint) that would need to support multiple parameter values being passed in a URL request. This has been a known , serious limitation for a long time. Now that integrated mode is the recommended method for delivery RS reports, this capability is absolutely critical.