<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Refreshing Reports using URL access in Reporting Services</title>
	<atom:link href="http://www.garry-stewart.com/blog/2009/07/09/refreshing-reports-using-url-access-in-reporting-services/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.garry-stewart.com/blog/2009/07/09/refreshing-reports-using-url-access-in-reporting-services/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=refreshing-reports-using-url-access-in-reporting-services</link>
	<description>A random collection of thoughts from an easily bored developer</description>
	<lastBuildDate>Thu, 22 Dec 2011 01:52:07 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.1</generator>
	<item>
		<title>By: Thomas Trung Vo</title>
		<link>http://www.garry-stewart.com/blog/2009/07/09/refreshing-reports-using-url-access-in-reporting-services/comment-page-1/#comment-339</link>
		<dc:creator>Thomas Trung Vo</dc:creator>
		<pubDate>Mon, 22 Aug 2011 14:31:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.garry-stewart.com/blog/?p=80#comment-339</guid>
		<description>Make Report by Reporting Service with SharePoint List http://sharepointtaskmaster.blogspot.com/2011/08/make-report-by-reporting-service-with.html</description>
		<content:encoded><![CDATA[<p>Make Report by Reporting Service with SharePoint List <a href="http://sharepointtaskmaster.blogspot.com/2011/08/make-report-by-reporting-service-with.html" rel="nofollow">http://sharepointtaskmaster.blogspot.com/2011/08/make-report-by-reporting-service-with.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Garry</title>
		<link>http://www.garry-stewart.com/blog/2009/07/09/refreshing-reports-using-url-access-in-reporting-services/comment-page-1/#comment-57</link>
		<dc:creator>Garry</dc:creator>
		<pubDate>Sat, 11 Jul 2009 03:35:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.garry-stewart.com/blog/?p=80#comment-57</guid>
		<description>You could have also made a simple form which, on submission, calls the Reporting Services web service using your form variables as parameters, then use your app to display the returning HTML 4.01 (or PDF or RTF or whatever you want). It&#039;s a SOAP payload so you can send up whatever you want (well, within the web server&#039;s set limits, of course).</description>
		<content:encoded><![CDATA[<p>You could have also made a simple form which, on submission, calls the Reporting Services web service using your form variables as parameters, then use your app to display the returning HTML 4.01 (or PDF or RTF or whatever you want). It&#8217;s a SOAP payload so you can send up whatever you want (well, within the web server&#8217;s set limits, of course).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel O</title>
		<link>http://www.garry-stewart.com/blog/2009/07/09/refreshing-reports-using-url-access-in-reporting-services/comment-page-1/#comment-56</link>
		<dc:creator>Daniel O</dc:creator>
		<pubDate>Sat, 11 Jul 2009 01:09:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.garry-stewart.com/blog/?p=80#comment-56</guid>
		<description>True, but then you have to commit it to provide preview access and clean it up if the user cancels out of the letter generation wizard or closes the window.

The real solution would have been if the customer let us have SQL 2008 RS, then we&#039;d just render it to word with the basic details from the DB, and then the user edits in the body of the letter directly in word.</description>
		<content:encoded><![CDATA[<p>True, but then you have to commit it to provide preview access and clean it up if the user cancels out of the letter generation wizard or closes the window.</p>
<p>The real solution would have been if the customer let us have SQL 2008 RS, then we&#8217;d just render it to word with the basic details from the DB, and then the user edits in the body of the letter directly in word.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Garry</title>
		<link>http://www.garry-stewart.com/blog/2009/07/09/refreshing-reports-using-url-access-in-reporting-services/comment-page-1/#comment-54</link>
		<dc:creator>Garry</dc:creator>
		<pubDate>Thu, 09 Jul 2009 10:39:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.garry-stewart.com/blog/?p=80#comment-54</guid>
		<description>Wouldn&#039;t it have made more sense to have a form that stores the stuff in an intermediate table and then just give it the ID of the letter you want to display in the report?</description>
		<content:encoded><![CDATA[<p>Wouldn&#8217;t it have made more sense to have a form that stores the stuff in an intermediate table and then just give it the ID of the letter you want to display in the report?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel O</title>
		<link>http://www.garry-stewart.com/blog/2009/07/09/refreshing-reports-using-url-access-in-reporting-services/comment-page-1/#comment-53</link>
		<dc:creator>Daniel O</dc:creator>
		<pubDate>Thu, 09 Jul 2009 10:05:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.garry-stewart.com/blog/?p=80#comment-53</guid>
		<description>Yes, we ended up implementing a form POST to address the limit. The reports being generated were letters, so the users would type in several paragraphs of text.</description>
		<content:encoded><![CDATA[<p>Yes, we ended up implementing a form POST to address the limit. The reports being generated were letters, so the users would type in several paragraphs of text.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Garry</title>
		<link>http://www.garry-stewart.com/blog/2009/07/09/refreshing-reports-using-url-access-in-reporting-services/comment-page-1/#comment-52</link>
		<dc:creator>Garry</dc:creator>
		<pubDate>Thu, 09 Jul 2009 07:39:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.garry-stewart.com/blog/?p=80#comment-52</guid>
		<description>These are fairly simple reports. In fact, I&#039;m using the logged in user to drive most of them so the only real parameter is my random parameter.

Out of interest, why are you passing in over 1500 characters worth of parameters? That sounds like a lot, even for a complex report.

It would also be interesting to see if you can do a POST (and therefore get around the character limit). Not exactly RESTful, but it might get you out of a jam.</description>
		<content:encoded><![CDATA[<p>These are fairly simple reports. In fact, I&#8217;m using the logged in user to drive most of them so the only real parameter is my random parameter.</p>
<p>Out of interest, why are you passing in over 1500 characters worth of parameters? That sounds like a lot, even for a complex report.</p>
<p>It would also be interesting to see if you can do a POST (and therefore get around the character limit). Not exactly RESTful, but it might get you out of a jam.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel O</title>
		<link>http://www.garry-stewart.com/blog/2009/07/09/refreshing-reports-using-url-access-in-reporting-services/comment-page-1/#comment-50</link>
		<dc:creator>Daniel O</dc:creator>
		<pubDate>Thu, 09 Jul 2009 07:18:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.garry-stewart.com/blog/?p=80#comment-50</guid>
		<description>One limitation we found from using the URL to pass in parameters is if you are passing in a large section of text (say over 1500 characters) you start to hit the limit of what can but on on a URL.</description>
		<content:encoded><![CDATA[<p>One limitation we found from using the URL to pass in parameters is if you are passing in a large section of text (say over 1500 characters) you start to hit the limit of what can but on on a URL.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

