Good afternoon, I've designed a Reporting Services report that has a multi-value parameter. The report works just great. The only issue I'm running into is that the users are complaining that when they want to select the values, within the multi-value parameter box, they have to scroll it to the sides way too much. This also makes them select values by mistake. Is there away to inscrease the width of the multi-value parameter box? Best regards.

I guess you can do that by changing the stylesheet provided for controlling the layout and style of report manager. If your clients are using report manager, then read on: There is a file called ReportingServices.css in Program Files\Microsoft SQL Server\MSSQL.X\Reporting Services\ReportManager\Styles. Edit that in notepad and locate a class called "msrs-multiValueDropDown" and in that class addwidth property as follows and save the file: .msrs-multiValueDropDown { border: 1px DarkGray solid; width: 200px; } Shyam

That could work, yes. I'll sure try it tomorrow when I get to work. My only problem with that approach is that it's an horizontal change. All reports will be affected unless theres a way to tell that report, or parameter, to use a specific sheet or value from the default sheet.

No, it cannot be done on a report by report basis. So, can you please mark my post as answer?

Hi , I am using Report Manager with SQL 2005 , i have added a multi value parameter and used the above method to widen the text box using the width: 200px; but it does not have any effect when i run the reports in the Report Manager, I have tryed deleting the reports and deploying it again, also restartedSQL Server Reporting Services,Is there somthing else I could or need to do ? Thanx Arvin

Has anyone gotten this to work yet? I tried it in both the ReportingServices.css and RSWebParts.css with no luck. Thanks, Ron

Any luck since this post? - I am having same trouble, with no joy from editing the style sheet. will need to edit codebehind by the looks of things..

I haven't heard a word from anyone about this. Maybe it will be corrected in SQL Server 2008.

Did anybody have any luck regarding this matteR?

Dear Shyam Sundar, I've encoutered the same problem and i havent got an answer from anybody yet. The trick you derscribed doesnt work...do you happed to know what is the correct way of doing this? thank you.

Hi, Are you using Report Manager or trying to embed the report in your application? This trick works only with Report Manager. Shyam

Hi, Of course. I understand. I'm using the report manager in this case. But the problem persists

Hi, I suggested the trick but I never tried it myself. I think thefollowing link might help you: http://weblogs.asp.net/jgalloway/archive/2006/12/12/reporting-services-add-a-logo-to-the-report-manager.aspx If it works let me know. Shyam PS: I am having VS 2008 which does not work with SQL Server 2005 Reporting services, so I am not able to test the Report manager.

Hello.Seen that, tried that i explored almost every class there is in the htmlviewer.css and reportingservices.css and nothing seems to work.i have another problem though...a bigger one.my parameters come from an analysis services cube, some related (year--> month) and some are not. almost all of them are multivalue.but when i try to subscribe to a report, some of them are populated during the creation of the subscription and some are not.In different reports the same parameter can be populated or not. i cannot spot the trend of the error...do you happed to know anything about a known bug or some fix for that? it totally seems like a bug.thank you.

I guess I can help you only when the real SQL 2008 is available and I install it on my machine I think I had faced that problem (quite sometime back). Iguess you should find a workaround instead of figuring out if it is a bug. Maybe you can transform the cube data to a database table by pushing it on a frequent basis. If I remember what I did to solve it, I will let you know. Shyam

Thanks! That would be great. I think ill just push URL's tousers for now.

So it seems SQL RS 2008 has the same problem, the multi-select enabled parameter is not configurable and is too narrow for most uses. Can anyone tell me I am wrong ?

There are two ways of modifying the width in 2005, not sure if it works in 2008. One is to modify the HtmlViewer.css file after you have setup SSRS to use it (http://msdn.microsoft.com/en-us/library/ms345247.aspx). After that is done, you can add the following to the file (Program Files\Microsoft SQL Server\MSSQL.#\Reporting Services\ReportServer\Styles) DIV#ctl144_ctl00_ctl01_divDropDown{width: 350px !important;} the ctl144 part hasn't changed on the 4 or five machines I've used this on, but this number may be different on your installation, the middle ctl00 has been constant, but you need to add multiple lines for the lastctl## increments based on the number of input controls on the screen. so you may need to add 20 or 30 of these to your css file and increment the last ctl## because you catch all the dropdowns in your report. The second way, is to use a modification of the javascript code at http://weblogs.asp.net/jgalloway/archive/2006/12/12/reporting-services-add-a-logo-to-the-report-manager.aspxthat Shyam also pointed out. If you read through all the code that loads the multi select window by doing a view source, you will see that it is based on the width of the visible textbox: Code Snippet function Show(){ var floatingEditor = document.getElementById(this.m_floatingEditorID); // only show if the editor is not currently visible. if (floatingEditor.style.display == "inline") return; // Set drop down and summary string to the same width to make it look like a drop down var visibleTextBox = document.getElementById(this.m_dropDownObject.m_visibleTextBoxID); floatingEditor.style.width = visibleTextBox.offsetWidth + "px"; floatingEditor.style.display = "inline"; // Call the drop down object to show the iframe this.m_dropDownObject.Show(); // Set the iframe height to our controls height var floatingIFrame = document.getElementById(this.m_dropDownObject.m_floatingIframeID); floatingIFrame.style.height = floatingEditor.offsetHeight; if (floatingEditor.childNodes[0].focus) floatingEditor.childNodes[0].focus();} Unfortunately, this function is hardcoded into a dll somewhere I guess.Plus the width of the textbox is set to size 28, and that is notchangable anywhere easily. However, now that we know that it is based on the txtValue input box (ctl144_ctl00_ctl01_txtValue for example) we can insert the following code into the ReportServices.js file (Program Files\Microsoft SQL Server\MSSQL.#\Reporting Services\ReportManager\js\ReportingServices.js): Code Snippet addLoadEvent(SetMultiSelectParamWidth); function addLoadEvent(fn) { if (window.addEventListener) window.addEventListener('load', fn, false) else if (window.attachEvent) window.attachEvent('onload', fn); } function SetMultiSelectParamWidth() { var headerDivs = document.getElementsByTagName('input'); for (var i=0;i<HEADERDIVS.LENGTH;I++)< P> { var idname = headerDivs[i].id; if (typeof idname != 'undefined' && idname.search(/txtValue/i)>0) { headerDivs[i].size='50'; } } } This runs after the page has finished loading and changes the width of any text box to 50, you can modify this at your leisure. Since the multiselect window size is based on the size of the textbox, we now have a larger multiselect window. Yay us. If you want to limit it to the dropdown text boxes only, you will have to add a loop that looks for matching _divDropDown controls and only modify the txtValue controls that match. Can't guarantee this works for everyone, but hope this helps. Haven't tried it on 2008 yet either. For any Microsoft guy that reads this, COME ON! This has been an issue since 2000. You add all sorts of useless *** to sql 2008 and can't fix a simple thing like this. Or even document the css classnames in reporting services. It isn't that much to do in the 10 years you have been developing this product. Shango

Well, here we are 4 years later and still no fix on this bug. (errrr ... I mean "feature" of course) Just another factor that's driving us away from using SSRS Report Manager. I'm thinking SSRS must be from the same development team that built SharePoint, based on the quality of the application. 'nuf said.

Me too I'm still looking for a solution to this, if someone found something... Thank you!Geozah