<?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: Looking Up Data On Different Sources</title>
	<atom:link href="http://blog.hoegaerden.be/2010/05/16/looking-up-data-on-different-sources/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.hoegaerden.be/2010/05/16/looking-up-data-on-different-sources/</link>
	<description>SQL Server, BI, .NET, IT and anything else I have been playing with.</description>
	<lastBuildDate>Wed, 08 Feb 2012 16:00:45 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Valentino Vranken</title>
		<link>http://blog.hoegaerden.be/2010/05/16/looking-up-data-on-different-sources/comment-page-1/#comment-3320</link>
		<dc:creator>Valentino Vranken</dc:creator>
		<pubDate>Wed, 12 Jan 2011 07:41:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hoegaerden.be/2010/05/16/looking-up-data-on-different-sources/#comment-3320</guid>
		<description>Hi Luke, thanks for adding a comment here!

(Luke initially emailed me with the same question, to which I responded.  But I wanted to be able to post the solution for everyone so I asked Luke to put the question as a comment to my article.)

Here&#039;s what I answered:

   1. To start, drag a Table from the Toolbox onto the report.
   2. Now, drag ProductAlternateKey from the dataset into the Detail-level cell of the first column.  Do the same for the EnglishProductName, but then into the second column.
   3. Now set up grouping on the Detail level.  One way to do that is through the Row Groups pane at the bottom of the Design window.  At the moment it only shows one item called Details.  Hit the small arrow to open up the context menu and select Group Properties.  Click the Add button under the Group Expressions label and group on ProductAlternateKey.  Close the properties window
   4. Set up the third remaining column by selecting OrderQuantity from the left-click context menu.  (That probably didn&#039;t make much sense.  When you hover the mouse pointer above the empty cell, you see a small icon of a table appear.  Click that to get a list of all the fields in the dataset and select OrderQuantity.)

Grouping on the Detail level has now been set up completely.  You can render the report to have a look at the current result.  Next up is adding the group levels above the detail level.

   1. With the table selected, we&#039;ll again use the Row Groups pane.  Click the dropdown to get the context menu and select Add Group &gt; Parent Group.  Choose the [EnglishProductSubcategoryName] field to group by and also activate the &quot;Add group header&quot; checkbox.
   2. That will create a new column in front of the three we already set up.   But that&#039;s not what we want.  So, right-click the grey top of the new column and choose Delete Columns.
   3. In the new header row that&#039;s currently empty, select the [EnglishProductSubcategoryName] field.  To get the header to display over all three columns, you can select all three cells of the row, right-click and choose Merge Cells.

That&#039;s one level of grouping added.  To add the next one, the system is exactly the same.  Only difference is that now you need to add a Parent Group to the &quot;EnglishProductSubcategoryName&quot; group in the Row Groups pane.  And obviously you now need to group on [EnglishProductCategoryName].

Have fun, and thanks again for your question!
Valentino.</description>
		<content:encoded><![CDATA[<p>Hi Luke, thanks for adding a comment here!</p>
<p>(Luke initially emailed me with the same question, to which I responded.  But I wanted to be able to post the solution for everyone so I asked Luke to put the question as a comment to my article.)</p>
<p>Here&#8217;s what I answered:</p>
<p>   1. To start, drag a Table from the Toolbox onto the report.<br />
   2. Now, drag ProductAlternateKey from the dataset into the Detail-level cell of the first column.  Do the same for the EnglishProductName, but then into the second column.<br />
   3. Now set up grouping on the Detail level.  One way to do that is through the Row Groups pane at the bottom of the Design window.  At the moment it only shows one item called Details.  Hit the small arrow to open up the context menu and select Group Properties.  Click the Add button under the Group Expressions label and group on ProductAlternateKey.  Close the properties window<br />
   4. Set up the third remaining column by selecting OrderQuantity from the left-click context menu.  (That probably didn&#8217;t make much sense.  When you hover the mouse pointer above the empty cell, you see a small icon of a table appear.  Click that to get a list of all the fields in the dataset and select OrderQuantity.)</p>
<p>Grouping on the Detail level has now been set up completely.  You can render the report to have a look at the current result.  Next up is adding the group levels above the detail level.</p>
<p>   1. With the table selected, we&#8217;ll again use the Row Groups pane.  Click the dropdown to get the context menu and select Add Group > Parent Group.  Choose the [EnglishProductSubcategoryName] field to group by and also activate the &#8220;Add group header&#8221; checkbox.<br />
   2. That will create a new column in front of the three we already set up.   But that&#8217;s not what we want.  So, right-click the grey top of the new column and choose Delete Columns.<br />
   3. In the new header row that&#8217;s currently empty, select the [EnglishProductSubcategoryName] field.  To get the header to display over all three columns, you can select all three cells of the row, right-click and choose Merge Cells.</p>
<p>That&#8217;s one level of grouping added.  To add the next one, the system is exactly the same.  Only difference is that now you need to add a Parent Group to the &#8220;EnglishProductSubcategoryName&#8221; group in the Row Groups pane.  And obviously you now need to group on [EnglishProductCategoryName].</p>
<p>Have fun, and thanks again for your question!<br />
Valentino.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Luke</title>
		<link>http://blog.hoegaerden.be/2010/05/16/looking-up-data-on-different-sources/comment-page-1/#comment-3312</link>
		<dc:creator>Luke</dc:creator>
		<pubDate>Wed, 05 Jan 2011 22:26:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hoegaerden.be/2010/05/16/looking-up-data-on-different-sources/#comment-3312</guid>
		<description>Hi Valentino

Thanks for a helpful post.

This question relates to your report layout rather than data sources...

In your first screenshot the groups are displayed on top of each other. That is, [EnglishProductCategoryName] is stacked on top of [EnglishProductSubcategoryName], which is stacked on top of the data row.

I&#039;m using SSRS 2008 R2 and haven&#039;t been able to replicate that, and it&#039;s driving me nuts!  The only way I can seem to organise the groups is by having a new column for each group, not a new row like yours.

Would you mind outlining please how you built the report layout in your screenshots above?

Many thanks in advance,
Luke.</description>
		<content:encoded><![CDATA[<p>Hi Valentino</p>
<p>Thanks for a helpful post.</p>
<p>This question relates to your report layout rather than data sources&#8230;</p>
<p>In your first screenshot the groups are displayed on top of each other. That is, [EnglishProductCategoryName] is stacked on top of [EnglishProductSubcategoryName], which is stacked on top of the data row.</p>
<p>I&#8217;m using SSRS 2008 R2 and haven&#8217;t been able to replicate that, and it&#8217;s driving me nuts!  The only way I can seem to organise the groups is by having a new column for each group, not a new row like yours.</p>
<p>Would you mind outlining please how you built the report layout in your screenshots above?</p>
<p>Many thanks in advance,<br />
Luke.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Implementing Data Bars In A Grouped Table &#171; A Blog for SQL Server Reporting Services (SSRS) Programmers</title>
		<link>http://blog.hoegaerden.be/2010/05/16/looking-up-data-on-different-sources/comment-page-1/#comment-2611</link>
		<dc:creator>Implementing Data Bars In A Grouped Table &#171; A Blog for SQL Server Reporting Services (SSRS) Programmers</dc:creator>
		<pubDate>Fri, 11 Jun 2010 08:11:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hoegaerden.be/2010/05/16/looking-up-data-on-different-sources/#comment-2611</guid>
		<description>[...] Bars In A Grouped Table  By Valentino Vranken, on June 11th, 2010 Earlier I wrote an article about the new lookup functions that ship with SQL Server 2008 R2.  Today I’m going to show you another new feature of SSRS 2008 [...]</description>
		<content:encoded><![CDATA[<p>[...] Bars In A Grouped Table  By Valentino Vranken, on June 11th, 2010 Earlier I wrote an article about the new lookup functions that ship with SQL Server 2008 R2.  Today I’m going to show you another new feature of SSRS 2008 [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: A Developer&#39;s Blog &#183; Implementing Data Bars In A Grouped Table</title>
		<link>http://blog.hoegaerden.be/2010/05/16/looking-up-data-on-different-sources/comment-page-1/#comment-2563</link>
		<dc:creator>A Developer&#39;s Blog &#183; Implementing Data Bars In A Grouped Table</dc:creator>
		<pubDate>Thu, 27 May 2010 20:16:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hoegaerden.be/2010/05/16/looking-up-data-on-different-sources/#comment-2563</guid>
		<description>[...] Subscribe to feed &#8249; Looking Up Data On Different Sources [...]</description>
		<content:encoded><![CDATA[<p>[...] Subscribe to feed &lsaquo; Looking Up Data On Different Sources [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Valentino Vranken</title>
		<link>http://blog.hoegaerden.be/2010/05/16/looking-up-data-on-different-sources/comment-page-1/#comment-2538</link>
		<dc:creator>Valentino Vranken</dc:creator>
		<pubDate>Tue, 18 May 2010 06:18:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hoegaerden.be/2010/05/16/looking-up-data-on-different-sources/#comment-2538</guid>
		<description>Hello Andrew,

I see what you mean, it looks indeed like this won&#039;t be possible.  The only way that I can think of to get this accomplished - and still use the lookup functions - is by somehow adding the different key values together into one concatenated value.

Thanks for your comment!
Valentino.</description>
		<content:encoded><![CDATA[<p>Hello Andrew,</p>
<p>I see what you mean, it looks indeed like this won&#8217;t be possible.  The only way that I can think of to get this accomplished &#8211; and still use the lookup functions &#8211; is by somehow adding the different key values together into one concatenated value.</p>
<p>Thanks for your comment!<br />
Valentino.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew</title>
		<link>http://blog.hoegaerden.be/2010/05/16/looking-up-data-on-different-sources/comment-page-1/#comment-2537</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Tue, 18 May 2010 05:11:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hoegaerden.be/2010/05/16/looking-up-data-on-different-sources/#comment-2537</guid>
		<description>Thanks for your blog post.

It seems as though only one level of lookup is supported.

How would I go about matching another key pair?</description>
		<content:encoded><![CDATA[<p>Thanks for your blog post.</p>
<p>It seems as though only one level of lookup is supported.</p>
<p>How would I go about matching another key pair?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

