{"id":20,"date":"2008-09-24T13:07:05","date_gmt":"2008-09-24T17:07:05","guid":{"rendered":"http:\/\/blogs.law.harvard.edu\/brandonhaynes\/?p=20"},"modified":"2008-09-26T14:56:52","modified_gmt":"2008-09-26T18:56:52","slug":"changing-the-size-of-reportviewer-parameter-dropdown-list","status":"publish","type":"post","link":"https:\/\/archive.blogs.harvard.edu\/brandonhaynes\/2008\/09\/24\/changing-the-size-of-reportviewer-parameter-dropdown-list\/","title":{"rendered":"Changing the Size of ReportViewer Parameter Dropdown List"},"content":{"rendered":"

\"SSRS<\/a>I recently encountered an issue with the SSRS ReportViewer<\/a> control where the parameter drop-down list was of insufficient width for the parameters contained therein.\u00a0 Surprisingly, a search<\/a>\u00a0yielded no solutions.\u00a0 Indeed, several individuals indicated that changing this width was not possible.<\/p>\n

Fortunately, it does turn out to be possible.<\/p>\n

<\/p>\n

Firing up the IE developer toolbar<\/a>, I immediately noted that (a) parameter controls were rendered outside the document hierarchy (in this case at the end of the FORM), (b) there was no class specified anywhere within the internal ReportViewer tag hierarchy, and (c) styles were hard-coded directly on the DIV tag which held the drop-down list (implemented as a TABLE).\u00a0 Indeed, the width attribute on this DIV was\u00a0hard-coded at 184px.\u00a0 By default, the parameters dropdown appears as:<\/p>\n

<\/a><\/p>\n

Fortunately, while there was no specific class to hang a custom width from, it turns out that the id of this DIV was reliably predictable.\u00a0 As such, a judiciously constructed style could indeed target (and thereby style) this tag.<\/p>\n

The form of the id on the DIV in question is [Viewer ClientId]_ctl00_ctl03_divDropDown.\u00a0 Here, ctl00\u00a0is the automatically-generated id of the Microsoft.Reporting.WebForms.ParametersArea control, and ctl03 is the id of the Microsoft.Reporting.WebForms.MultiValueValidValuesControl.<\/p>\n

Putting this together, an initial style would read as:<\/p>\n

<<\/span>style<\/span> <\/span>type<\/span>=”text\/css”>
\n<\/span>\u00a0\u00a0\u00a0\u00a0 DIV#<%=<\/span> <\/span>Viewer.ClientID<\/span> %<\/span>><\/span>_ctl00_ctl03_divDropDown<\/span>
\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 {
\n<\/span><\/span>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 width<\/span>: <\/span>320px<\/span> <\/span>!important<\/span>;
\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 }
\n<\/span><\/span><\/span><\/<\/span><\/span>style><\/span><\/span><\/span><\/p>\n

<<\/span><\/span><\/span>rsweb<\/span>:<\/span>ReportViewer<\/span> <\/span>ID<\/span>=”Viewer”<\/span> <\/span>runat<\/span>=”server”<\/span> <\/span>Width<\/span>=”100%”<\/span> <\/span>Height<\/span>=”600px”<\/span> <\/span>ProcessingMode<\/span>=”Remote”<\/span> <\/span>\/><\/span><\/p>\n

\"SSRS<\/a>Here we use the ClientID the ReportViewer (and its constituent ctl00 and ctl03 child and grandchild, respectively).\u00a0 We also use an “!important” declaration to override the inline styling.\u00a0 After our style is applied, the ReportViewer dropdown may be set to any size.<\/p>\n

Note that it would be of better form to create a custom function that recurses the ReportViewer control hierarchy to locate the divDropDown control (and use its ClientID).\u00a0 This would make the solution a bit more forward-looking and upgrade-friendly.\u00a0 I leave this as an exercise to the reader (there are plenty of tutorials<\/a> out there about recursing the control tree).<\/p>\n

Hope this helps anyone needing to resize this particular control.<\/p>\n

B<\/p>\n","protected":false},"excerpt":{"rendered":"

I recently encountered an issue with the SSRS ReportViewer control where the parameter drop-down list was of insufficient width for the parameters contained therein.\u00a0 Surprisingly, a search\u00a0yielded no solutions.\u00a0 Indeed, several individuals indicated that changing this width was not possible. Fortunately, it does turn out to be possible.<\/p>\n","protected":false},"author":1933,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3129,142],"tags":[3110,19471,3130,3108,3109],"class_list":["post-20","post","type-post","status-publish","format-standard","hentry","category-microsoft-sql-server-reporting-services-ssrs","category-technology","tag-microsoft-reporting-services","tag-microsoft-sql-server-reporting-services-ssrs","tag-reporting-services","tag-reportviewer","tag-ssrs"],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/archive.blogs.harvard.edu\/brandonhaynes\/wp-json\/wp\/v2\/posts\/20","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/archive.blogs.harvard.edu\/brandonhaynes\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/archive.blogs.harvard.edu\/brandonhaynes\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/brandonhaynes\/wp-json\/wp\/v2\/users\/1933"}],"replies":[{"embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/brandonhaynes\/wp-json\/wp\/v2\/comments?post=20"}],"version-history":[{"count":1,"href":"https:\/\/archive.blogs.harvard.edu\/brandonhaynes\/wp-json\/wp\/v2\/posts\/20\/revisions"}],"predecessor-version":[{"id":480,"href":"https:\/\/archive.blogs.harvard.edu\/brandonhaynes\/wp-json\/wp\/v2\/posts\/20\/revisions\/480"}],"wp:attachment":[{"href":"https:\/\/archive.blogs.harvard.edu\/brandonhaynes\/wp-json\/wp\/v2\/media?parent=20"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/brandonhaynes\/wp-json\/wp\/v2\/categories?post=20"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/brandonhaynes\/wp-json\/wp\/v2\/tags?post=20"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}