I have a bunch of site collections that all have a identical list( status, Title, Date). I am trying to create a master list on my site that grabs the items from each lists and displays them all together with one extra column called ( Owner ) which will say where the item came from (which site it was on). Can anyone point me in the right direction on how to accomplish this? Is this possible with built in features or do i need to build something custom? Anything to get me started woulf be great. I am using share point 2010. thanks.

Edit - the combined list will not need full functionality, all I plan to do id have the title be a link to the item on its own site collection.

Edit -

There will be something like 5-10 site collections with one list from each site collection. the list is a task list and we want to combine them all and allow sorting and grouping to get a better handle on all of the tasks needed to be done. this will be accessed multiple times a day so i think a custom web part is a good way to handle it. I have started developing a custom visual web part but I am having a hard time accomplishing what i want. Right now i have a standard table where I pull the lists values into, this is good for displaying all task items but it does not allow me to sort or group the items afterwards (unless I am missing something).

Does this further info help?

1 Answer 1


Because you are going across site collection boundaries, your options are:

  • Search - Provided you have these lists created with a the same content type for the list items, you could create a search scope to return the items of this content type. You might need to adjust the search results XSL a bit to meet your needs. You might reference this link: http://sharepoint.licomputersource.com/2010/11/configure-custom-search-scope-in-sharepoint-2010-to-rollup-tasks-documents-or-sites-from-anywhere-part-1/ (found with a quick Bing search). Also, this link should help get going with using the Search Results web part and customizing the query/display: http://msdn.microsoft.com/en-us/library/ee819886. If the requirement is to see all items, regardless of item permissions, this won't work.
  • Custom Developed - If the requirement is to see all items, regardless of permissions to actually get at them, you might look to a custom solution. You might store references to all items in a master list somewhere. This could be done from a Timer Job (probably my first choice), Workflow, or Event Receiver, depending on what the security/access permissions were. Depending on how many site collections you are talking about, and assuming you could work in a Farm Solution (not Sandboxed), you might be able to leverage the Server Side Object Model in a web part, but this could be asking for trouble to do that aggregation each time (if you did pursue this, I'd look at caching the data).
  • Purchased - the big vendors may have things that aggregate across lists. Bamboo comes to mind. As mentioned in comments, Lightning Tools (http://www.lightningtools.com/lightning-conductor-2010-web-part.aspx). Cannot speak to either as I've not used them personally.
  • PowerShell - if this is only needed by a small subset of users (like 1-2), you might also consider a PowerShell script that is run as a scheduled task which dumps the results to a .csv (comma separate file), then import this data into a list. You could import with PowerShell, or manually using DataSheet View. Once loaded into a list, you could then use the standard list web parts for display.

Hope this helps.

  • and Lightning Tools. Commented Jun 13, 2012 at 20:26
  • After reading you answer let me clarify a few things. I will definitely have permissions to all lists and items, this is being used as a way to see tasks from many different lists at once. So it looks like the first suggestion may be the way to go but I am a bit confused. I was tasked with creating a web part to accomplish this. Can you clarify a bit what you mean by using search? I come from a developer background but i am new to share point so some of the terminology is still a little confusing to me.
    – kds6253
    Commented Jun 13, 2012 at 20:43
  • added a blog reference that i think pretty closely matches what you are trying to do.
    – Brian
    Commented Jun 14, 2012 at 1:46
  • Add more info to your original posting to help get better responses. For example, how many site collections, how many lists in each site collection? how many list items per list? How often will this be needed (for example if you just need to run it weekly, you might be better off just writing a powershell script to output the results and upload the results as an custom list and/or excel document). As you'll see with SP, there are many ways to accomplish a given task. Key is finding the right one for your specific scenario.
    – Brian
    Commented Jun 14, 2012 at 1:50

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.