Our environment... SharePoint Foundations 2010, SQL Server 2008 R2, SSRS 2008 R2 in SP integration mode... We have two SharePoint lists - one is the default Tasks and the 2nd list is Titled Business_Unit. The Tasks list has been modified by adding a new lookup column (allows multi-select) which populates from a 2nd list titled Business Unit. Okay - not much craziness going on there. We're trying to produce a SSRS 2008 via BIDS which groups on the BU value - however having a difficult time getting the grouping to work due to how the query results are returned from the SharePoint List. Simple enough, we can add two data sets in the .rdl - one for each SharePoint List - no problem. BU_dataset has two fields "Business_Unit" and "Active", we filter that "Active" is equal to "true". Tasks_data set has five fields "Title", "Status", "Due Date", "Assigned to", and "Business Unit" - we filter on Status equal to "Completed" However, while trying to build a relationship between the two datasets I am a bit stuck. The results in the Tasks dataset for the "Business Unit" field appear as follows (just some examples): if a single business unit is selected, it appears nice and clean such as simply "Accounting", or "HR", etc.. however, if multiple items are selected, the results are a bit unclean "Accounting;#2;#Administrative;#3;#Brazil;#4;#IT;#5;#HR;#9" If we simply try to Group on the Tasks dataset's "Business Unit" field, it views the "multiple select" line items as a single item. How can we trick SSRS in to grouping by the Business Unit dataset, and then populate rows (even duplicates) with Tasks where the Tasks Business Unit field contains the Group parameter? Parent [Business Unit] (from business unit dataset) Child Rows [Tasks] {details rows from Tasks data set} - filtered where [Tasks].[Business Unit] contains [Parent].[Business Unit] Thanks, Rich

I should add, we can get this to work by using a subreport inside a table... we are trying to learn how to do this without using a subreport inside a table.

Hi Landho, It seems we could not achieve this without subreport. Thanks for your understanding. Thanks, Challen FuPlease remember to mark the replies as answers if they help and unmark them if they provide no help.