Home Dashboard Directory Help
Search

SSRS Manage Parameters in SharePoint 2010 - Dynamic Parameter Values Not Loaded by im2pky


Status: 

Closed
 as Duplicate Help for as Duplicate


4
0
Sign in
to vote
Type: Bug
ID: 696890
Opened: 10/26/2011 1:18:41 PM
Access Restriction: Public
0
Workaround(s)
view
2
User(s) can reproduce this bug

Description

Microsoft Premier Support Ticket Created - ID = 111102156474056

Issue Definition: When trying to set default values for a parameter that is populated by a query no values are in the pick list
If they run the report the picklist for the parameter is populated
This is happening with multi-select parameters

This used to work fine in MOSS 2007
They ran into this issue after upgrading to SharePoint 2010
Scope Agreement: This case will be considered resolved when a solution for the parameter picklist issue is determined.

Resolution of the initial investigation -

Microsoft Support - I have been researching this behavior and have not found any indication it is by design. It has not been reported as a bug either. I will submit it as a bug to the product group. They will review it and if it is determined to be a bug it will hopefully be fixed in a future release.
If you don’t have any questions, once I have submitted the report I will close the case.

Other Comments -

Microsoft Support - There isn’t a process for doing that. You can email me with the case number and I can check on it to see what the status is. There is another option. You can report this to the product group at connect.microsoft.com. Then you would be able to check on the status and get feedback from the product group.
Details
Sign in to post a comment.
Posted by kmoormann on 1/31/2014 at 2:30 PM
This is closed as duplicate but there is no link available to the issue in which is this a duplicate of
Posted by eric.stephani on 3/1/2012 at 6:44 AM
We are experiencing this issue also.
Posted by Chris L. Otte on 2/7/2012 at 3:05 PM
We have the same issue. It is suppose to be resolved with SP 2 for 2k8 R2 and 2012.
Sign in to post a workaround.