<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Blogging about all things SAS &#187; SAS Web report Studio exports null</title>
	<atom:link href="http://blog.saasinct.com/tag/sas-web-report-studio-exports-null/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.saasinct.com</link>
	<description>::       Sharing with the world everything we discover about SAS.</description>
	<lastBuildDate>Wed, 01 Sep 2010 06:56:10 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Begon damn dots (or how to remove nulls in an OLAP cube)</title>
		<link>http://blog.saasinct.com/2009/07/02/begon-damn-dots-or-how-to-remove-nulls-in-an-olap-cube/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=begon-damn-dots-or-how-to-remove-nulls-in-an-olap-cube</link>
		<comments>http://blog.saasinct.com/2009/07/02/begon-damn-dots-or-how-to-remove-nulls-in-an-olap-cube/#comments</comments>
		<pubDate>Wed, 01 Jul 2009 22:01:31 +0000</pubDate>
		<dc:creator>Shane Gibson</dc:creator>
				<category><![CDATA[SAS 9.1]]></category>
		<category><![CDATA[SA OLAP .]]></category>
		<category><![CDATA[SAS Web report Studio exports null]]></category>

		<guid isPermaLink="false">http://blog.sasinct.com/2009/07/02/begon-damn-dots-or-how-to-remove-nulls-in-an-olap-cube/</guid>
		<description><![CDATA[If you create a SAS OLAP cube in 9.1.x and their is some some sparsity in the values (when is there not) then you will end up with lots of .&#8217;s when no values exist for an intersection. This is not really a problem till you use Web Report Studio to report off the cube [...]]]></description>
			<content:encoded><![CDATA[<p>If you create a SAS OLAP cube in 9.1.x and their is some some sparsity in the values (when is there not) then you will end up with lots of .&#8217;s when no values exist for an intersection.</p>
<p>This is not really a problem till you use Web Report Studio to report off the cube and then the user exports the report to excel in a non formatted format.</p>
<p>When they do this the . is passed to excel and then Excel refuses to apply formulas nicely when creating them on these cells (funnily enough the Excel sum formula does work for these).</p>
<p>So in this case you want to force WRS to show .&#8217;s as 0 and then they export as 0&#8242;s and excel is happy (or you can force the users to manually search and replace them each time they export if you are so inclined).</p>
<p>So the work around for us was to create a custom measure in the information map that changed all the .&#8217;s to 0&#8242;s.  the MDX for this was:</p>
<p><font color="#999999">IIF(&lt;&lt;Measures.Cost&gt;&gt;.Value =  null , 0 , &lt;&lt;Measures.Cost&gt;&gt;)</font></p>
<p>Of course the down side of this is that the OLAP server has to do the calc each time it renders the values rather than a look up.</p>
<p>In hindsight we could have created a custom measure in the OLAP cube that did this and it would be calculated during the cube build rather than during the report rendering.</p>
<p><a class="a2a_dd addtoany_share_save" href="http://www.addtoany.com/share_save"><img src="http://blog.saasinct.com/wp-content/plugins/add-to-any/share_save_256_24.png" width="256" height="24" alt="Share/Bookmark"/></a> </p>]]></content:encoded>
			<wfw:commentRss>http://blog.saasinct.com/2009/07/02/begon-damn-dots-or-how-to-remove-nulls-in-an-olap-cube/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
