I'm not sure if this feature already exists, but if not - Web Part Connections for the properties.

Lets say I have a set of web sites for each user, which I would like to aggregate information from. It would be very useful, if I could write my own WP that supplies the sites list to the Rollup WP, thus allowing me to identify the logged-on user and perform my own business logic.

Thanks, for your comment, I suppose that you want query a list that has a field with the subsites if the condition is true, get the field that contains the subsite and rollup the subsite. Is correct?
Csegura

Hi Carlos, I would just like what we spoke about on the forum at http://foros.ideseg.com/viewtopic.php?t=17 - that is having better support for rolling up all lists named the same thing in subsites.
- Alex

Hello Carlos,
I didn't quite understand what you meant but I'll try to explain myself better:
I have my own Web Part that identifies the logged on user. Each of my users have a set of web sites that they need their information gathered from.
I can identify the user, get the collection of sites, and query each one seperately.
Or - I can use Web Part Connections, and supply your Web Part a string with the site list.

So the query will be fixed, but it will rollup from different sites, according to the connection.

Another option is that I have a Links List, and each link in the list is a URL of a Site Collection. Each Site Collection is related to another project. By allowing the user to choose the Site Collection he wants to rollup from, he can see different information about projects.

Please note that I do not intend to query a list to get the sites list string, but rather use the Web Part Connection Interface between two Web Parts on the same page.

I hope my examples make this clear.
Thanks and keep on the good work!
Dor.

Alex,
This feature is already in version 2 for sites and subsites.
csegura

When next version redy?

At the end of this week. I think :-)
carlos.

With version 2 of the Rollup webpart, the ability to search "Lists in all subsites" is an extremely useful feature. However, one thing that could be added to version 3 is to extend that feature so that you can tell it where to start searching from.

Example:

Lets say you have a user that places your webpart on /sites/mysite, but there is an events list on /sites/allsites/subsite1 that has data he wants to roll-up to his mysite. You can do that right now by specifically typing in the location of that events lists in the "Lists" field (i.e. type in /sites/allsites/subsite1:Events)

Lets say this user wants to roll-up all Events list from all subsites underneath /sites/allsites (i.e. /sites/allsites/subsite1, /sites/allsites/subsite2, /sites/allsites/subsite3....etc). Right now, unless he places the webpart on /sites/allsites and uses the "Lists in all subsites" option, the only other way he can aggregate this data to his mysite is to use the Lists field and type in all the locations that has the data (i.e. type in /sites/allsites/subsite1:Events,/sites/allsites/subsite2:Events...etc.) The user has two options - either place the webpart on /sites/allsites where it will automatically rollup the data for all subsites (he cannot put it on his mysite in this case), or manually maintain the locations where he wants to pull his data from (he can then put the webpart on his mysite, but has to manually change/update it everytime someone adds new sites)

This makes it extremely cumbersome for a user to maintain - especially when you consider that new subsites could be getting added daily. Similiar to what Dor suggested earlier where you could use webpart connections to pass this list onto your webpart, what I suggest is to allow the user to pass a variable called "RootURL" to your webpart that will tell it to include Lists on all subsites but only starting from the root the user specifies. That way the user tells it to use "/sites/allsites" as his "RootURL", he can put the webpart on /sites/mysite - but it will search for data on sites under /sites/allsites.

I hope I was able to explain that well enough. I must say though that you did an excellent job so far, this is only a suggestion. Keep up the good work!

kbui

Hello Carlos,

Great Job!! It is a breeze to install the webpart and to create the XSL. One thing I found out is that, this webpart does not work for Portal areas. Is this by design?

Do you have plans for developing this?

Thanks
Raj