Tag Info

Hot answers tagged

10

Yes this can be achieved by using an SPSiteDataQuery. See: http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.spsitedataquery.aspx. This will require some programming. If you do not want to develop against the SharePoint Object model, then use the Content Query Webpart (requires SharePoint Publishing Infrastructure feature activated). You will ...


5

There are a few products in the market that currently do this, for example Lightning Conductor by Lightning Tools: http://www.lightningtools.com/lightning-conductor-2010-web-part.aspx. This tool (I think) can even rollup across web applications too.


3

According to this hotfix document, build 14.0.5136.5002 of the cumulative update package fixes this problem. Issues that this hotfix package fixes Assume that you have a Site Aggregator web part on a Microsoft SharePoint Server 2010 site. When you try to add a site to the web part, there is no such a button that lets you to do this.


3

I was able to get this working by changing the DataMappings, and DataMappingViewFields. The values in these fields are very sensitive and a space or semi-colon in the wrong place will break it. I've posted what worked below, hopefully this will save someone else two days of misery! <property name="DataMappings" ...


3

Are you using MOSS or WSS only? If you have MOSS, have you tried the Content Query Web Part? If you really need to use the object model, you could try the SPSiteDataQuery class http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.spsitedataquery.aspx


2

Each blog will have its own RSS feed, so an RSS web part can help here. There is one provided however it only aggregates one feed at a time. If you don't mind setting up a web part page to show them all separately then that will work. Otherwise there are RSS web parts available that can combine multiple feeds together. A web search term like combine RSS ...


2

Have you looked in using the flexibilty of the the Data View Web Part using SharePoint Designer? I would think that seeing that the rollup, aggregation of data will be feasible seeing that are in the confines for one Site and/or Collection. The only think I question is the requirement to do an Excel Export. You won't be able export the data froma data ...


2

Im on the search wagon here. A way of avoiding the the indexing delay, you could build your own custom federated search web part that looks at SharePoint through the API (SPSiteDataQuery)


2

There are different choices: Search - not percise Cycle over site collections with SPSiteDataQuery Pre-aggregation to root site in each site collection with cycle over site collections Main problem in query over sitecollection - each site collectiom can be in different Content Database, witch can be on a different server.


2

The Data View Web Part (DVWP) will let you roll up all items across the Site Collection based on whatever criteria you define. It can be totally dynamic (not sure why Simon feels you need to keep it updated manually). The trick is the actual view. The Calendar view is a very complex view, and you won't be able to recreate it (at least I haven't ever been ...


2

As @Steve mentioned, create an Application Page in the _Layouts folder that outputs the RSS feed. Then link to that page from your web part. Here is an example of how to generate an RSS feed from C#: http://www.dailycoding.com/Posts/create_rss_feed_programatically_from_data_in_c.aspx


2

Content By Query Web Part is XSL based, by default, Title, Description, ImageUrl, and LinkUrl columns (if present) of the items that the query returns are rendered. The Web Part renders the ImageUrl column and the LinkUrl column as an image and as a hyperlink, respectively. If you want to query for custom content types and render specific columns from ...


1

You will need to create some custom XSLT which will allow you to present whatever fields you like. If you need a steer on this there are a couple of blog posts which may help - http://paylord.wordpress.com/2012/09/28/cqwp-and-xslt-part-1/


1

This is what you'll need using ID's: CopyUtil.aspx (what's in a name, right?) http://weblogs.asp.net/jan/archive/2008/02/26/copyutil-aspx-a-little-sharepoint-gem.aspx


1

You shouldn't need to use the /../../ method if you are directing to a _layouts page. You could simply do it as (not fully tested, going from memory): <a href="http://your.spdomain.com/{@FileDirRef.urlencodeasurl}/_layouts/listform.aspx?PageType=4&ListId={@ListId}&ID={@ID}">text</a>


1

I just hard coded (@REGION)=$groupfooter0 and into the $nodeset. I did this for every occurance. You may have to copy the xsl:variable in for groupfooter0 inside the xsl:when. I guess I don't understand why SPDesigner wouldn't do that by default. <xsl:with-param name="nodeset" select="msxsl:node-set($dvt_Rows)/root//Row[((@REGION)=$groupfooter0 and ...


1

What you're probably after is rollups with the Data View and SPDataSource I’ll give a brief overview of the SPDataSource control, as well as cover a pretty popular question: How do I create a view that rolls up data from across my site collection? See also http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.spsitedataquery.aspx ...


1

You could take other routes besides aggregating content types. One would be to create a data source in Designer and then bring in the columns directly from the other lists. Your xsl would get tricky b/c you woudl need to reference xpaths, which could affect performance but I've done amazing things using this method. Or you could create a new custom list ...


1

There is no way out of the box to aggregate all the RSS feeds in SharePoint into one feed. You would either have to build something, or you might consider looking at something like Yahoo Pipes (http://pipes.yahoo.com). Even with something like Yahoo Pipes you would have to add all the feeds manually into it's data stream.


1

I think you'll need an application page (_layouts page) for this that returns the xml needed for the feed. If you've seperated the data/business logic from your presentation layer in your webpart, then this application page should be pretty easy to write because you are just creating a new XML based presentation layer.


1

One other way to accomplish this would be to create an Event Receiver that is triggered when new blog posts are created. In the Event Receiver, check to see if the blog is indeed in a My Site and then push the link/title to a storage mechanism so that when you query the data with the webpart, it doesn't take forever to parse though every My Site blog. You ...


1

There is another web part that might buy yourself something. Take a look at the Content Query Web Part. This will roll up nicely based on the calendars, lists etc that are in a site collection. The only issue is that I doubt you could recreate the calendar vire you are after. You would use the Data View Web Part if you were trying to rollup a calendar ...


1

Here is a blog post I wrote about aggregating content in 2010. Most of it also applies to 2007 though. http://nextconnect.blogspot.com/2010/04/content-aggregation-in-sharepoint-2010.html Normally you look to roll up specific types of content like announcements or events. For content changes you may need to use the Search API to bring back entries based ...


1

I finally got this figured out. For some reason, whenever I tried to use ddwrt:UrlDirName it caused a problem when the HTML was produced for the browser. The URLs of the sub sites where not being passed correctly. It worked fine in SPD preview (design mode) but wouldn't display the same results in the browser. I ended changing the XSL sort expression and ...


1

We already talked about sorting by date descending and taking only the first item, but the added wrinkle here is that you have multiple lists. So if you want to get the latest item per list, you still will want to do the sorting, but sort by site, and then by date (descending). Then you can use the ddwrt:NameChanged function to determine, for each item, if ...


1

The linked data source in SharePoint Designer uses the AggregateDataSource class. AggregateDataSource.Sources The above is a collection of DataSource objects. AggregateDataSource.Aggregate This is a string similar to this: <concat name="data source"> <datasource name="Calendar" id="1" Type="SPList"/> <datasource name="Calendar2" ...



Only top voted, non community-wiki answers of a minimum length are eligible