<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Mark Brown's Blog : Reporting Services</title><link>http://blogs.msdn.com/mab/archive/tags/Reporting+Services/default.aspx</link><description>Tags: Reporting Services</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Ensure best Excel export formating from SQL Server Reporting Services</title><link>http://blogs.msdn.com/mab/archive/2007/06/28/ensure-best-excel-export-formating-from-sql-server-reporting-services.aspx</link><pubDate>Fri, 29 Jun 2007 03:49:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:3594961</guid><dc:creator>mab</dc:creator><slash:comments>3</slash:comments><comments>http://blogs.msdn.com/mab/comments/3594961.aspx</comments><wfw:commentRss>http://blogs.msdn.com/mab/commentrss.aspx?PostID=3594961</wfw:commentRss><wfw:comment>http://blogs.msdn.com/mab/rsscomments.aspx?PostID=3594961</wfw:comment><description>&lt;P&gt;When designing reports it is important to be aware that the report may be exported to Excel.&amp;nbsp;&amp;nbsp; This is most apparent when data manipulation must be done to satisfy the reporting requirements.&amp;nbsp;&amp;nbsp; SSRS exports to excel using the underlying data source and not the report formating itself.&amp;nbsp;&amp;nbsp; For example if you have stored in the database:&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Region&amp;nbsp;&amp;nbsp;&amp;nbsp; SalesPercent&lt;BR&gt;&lt;/STRONG&gt;West&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 10.5&lt;BR&gt;East&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 32.2&lt;/P&gt;
&lt;P&gt;If you want to display as a percent on the report&amp;nbsp;you might be tempted to use the format string "0.0\%" on your report layout.&amp;nbsp;&amp;nbsp; Ok, that gets the presentation but when you export to excel you get 10.5\% in the cell which appears to be 10.5 for excel and not .105 or 10.5%.&lt;/P&gt;
&lt;P&gt;To help, you may want to tackle the issue of display at the source.&amp;nbsp;&amp;nbsp; For example in the datasource for the report (the Select statement if you will), divide by 100 and then use the report format of "P".&amp;nbsp; An example select would be:&lt;/P&gt;
&lt;P&gt;SELECT Region. SalesPercent/100 as SalesPercent FROM SalesDataTable&lt;/P&gt;
&lt;P&gt;Hope this article gets you thinking about aspects you need to address when design and deploying reports that export data.&lt;/P&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=3594961" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/mab/archive/tags/Reporting+Services/default.aspx">Reporting Services</category></item><item><title>How to create a hyperlink in Reporting Services that opens in a new window</title><link>http://blogs.msdn.com/mab/archive/2007/05/17/how-to-create-a-hyperlink-in-reporting-services-that-opens-in-a-new-window.aspx</link><pubDate>Thu, 17 May 2007 21:35:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:2700008</guid><dc:creator>mab</dc:creator><slash:comments>4</slash:comments><comments>http://blogs.msdn.com/mab/comments/2700008.aspx</comments><wfw:commentRss>http://blogs.msdn.com/mab/commentrss.aspx?PostID=2700008</wfw:commentRss><wfw:comment>http://blogs.msdn.com/mab/rsscomments.aspx?PostID=2700008</wfw:comment><description>&lt;P&gt;I was at a client and the question came up "Can I jump to another web based tool from my report?".&amp;nbsp;&amp;nbsp; The answer seemed obvious ... YES.&amp;nbsp;&amp;nbsp; What was not straightfoward was how to&amp;nbsp;open the other web based tool in another window.&amp;nbsp;&amp;nbsp; Here is a solution a&amp;nbsp;found (someone else's idea) that helped.&lt;/P&gt;
&lt;P&gt;When designing the report:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Open up&amp;nbsp;a text box properties window&lt;/LI&gt;
&lt;LI&gt;Go to &lt;STRONG&gt;Navigation&lt;/STRONG&gt;&lt;/LI&gt;
&lt;LI&gt;Enable &lt;STRONG&gt;Jump to URL&lt;/STRONG&gt;&lt;/LI&gt;
&lt;LI&gt;In the URL enter &lt;STRONG&gt;javascript:void(window.open( 'http://www.microsoft.com', '_blank')&amp;nbsp;&lt;/STRONG&gt;&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;Please note that you should replace the &lt;A href="http://www.microsoft.com/" mce_href="http://www.microsoft.com/"&gt;http://www.microsoft.com&lt;/A&gt; with the URL you would like to launch.&amp;nbsp;&amp;nbsp; Also note, that the second parameter of '_blank' is the standard window.open target meaning a new window.&lt;/P&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=2700008" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/mab/archive/tags/SQL+Server/default.aspx">SQL Server</category><category domain="http://blogs.msdn.com/mab/archive/tags/Reporting+Services/default.aspx">Reporting Services</category></item><item><title>SQL Server 2005 SP2 is now available</title><link>http://blogs.msdn.com/mab/archive/2007/02/20/sql-server-2005-sp2-is-now-available.aspx</link><pubDate>Tue, 20 Feb 2007 19:22:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1727534</guid><dc:creator>mab</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/mab/comments/1727534.aspx</comments><wfw:commentRss>http://blogs.msdn.com/mab/commentrss.aspx?PostID=1727534</wfw:commentRss><wfw:comment>http://blogs.msdn.com/mab/rsscomments.aspx?PostID=1727534</wfw:comment><description>&lt;P&gt;For those anxiously awaiting, SQL Server 2005 SP2 is now available at &lt;A href="http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/servicepacks/sp2.mspx"&gt;http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/servicepacks/sp2.mspx&lt;/A&gt;&lt;/P&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=1727534" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/mab/archive/tags/SQL+Server/default.aspx">SQL Server</category><category domain="http://blogs.msdn.com/mab/archive/tags/Reporting+Services/default.aspx">Reporting Services</category></item><item><title>Reporting Services and #ERROR in cells</title><link>http://blogs.msdn.com/mab/archive/2007/02/20/reporting-services-and-error-in-cells.aspx</link><pubDate>Tue, 20 Feb 2007 18:57:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1727243</guid><dc:creator>mab</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/mab/comments/1727243.aspx</comments><wfw:commentRss>http://blogs.msdn.com/mab/commentrss.aspx?PostID=1727243</wfw:commentRss><wfw:comment>http://blogs.msdn.com/mab/rsscomments.aspx?PostID=1727243</wfw:comment><description>When writing a reporting services report sometimes it is impossible to evaluate all errors in desing mode.&amp;nbsp;&amp;nbsp; Occasionally, you may run across that the report runs but a single cell my return a #ERROR instead of the value expected.&amp;nbsp;&amp;nbsp; Sometimes this is caused by an invalid type being sent through a format expression for example.&amp;nbsp;&amp;nbsp; To eliminate the #ERROR, first check the data source to ensure the values are what you expect, then secondly code your expressions to satisfy your output using conversion formulas such as CINT().&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=1727243" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/mab/archive/tags/Reporting+Services/default.aspx">Reporting Services</category></item></channel></rss>