Tag Info

Hot answers tagged

10

You can use ParameterBindings to this purpose. <ParameterBinding Name="Language" Location="Resource(wss,language_value)" /> This will return "en-us" for English locale in xsl:param "Language". Also, you can pass whole resource values this way. You can read more about this in Stefan Stanev's blog: ...


5

You'll need to make sure that the xsl:stylesheet declares the ddwrt namespace. To do this, you'll need to add this to your xsl:stylesheet declaration if it isn't there already, though in your case we know it isn't because you're getting an error: xmlns:ddwrt="http://schemas.microsoft.com/WebParts/v2/DataView/runtime" You can see more details on this idea ...


4

Don't be afraid of XSLT. This is going to give you a tremendous amount of power without having to develop or deploy anything in return for a little effort to understand it. I always recommend starting with an identity transform so that you can see the XML that is coming in, and then start adding templates to process the nodes you are interested in. Visual ...


4

After looking for ages for the answer to this I stumbled on it minutes after posting this question... Anyway, the answer is here: http://blogs.msdn.com/b/joshuag/archive/2009/03/25/custom-date-formats-in-sharepoint-xsl.aspx Summary: Reference the ddwrt namespace at the top of the itemstyle.xls ...


4

The Content Query web part is included in the SharePoint Standard SKU, which implies MOSS for the 2007 version of the product. | 2007| 2010| ----------|-----|-----| Standard | Y | Y | ----------|-----|-----| Foundation| N | N | I've tried to make a complete reference table of all the SharePoint 2010 out-of-the-box web parts.


4

To add your configured web part to the web part gallery, go to Site Settings and then to the web part gallery. You can then upload your .webpart file - the gallery behaves like a normal document library. This is fine for one-off or occasional use. To do this in a repeatable way you would need to develop a feature, to deploy the webpart definition to the ...


4

Because SharePoint convert special characters in the internal name. _x0040_ = @ - More about mappings for non-alphabetic characters So that means when that column was created, its title was @Active.


4

I'm guessing this is SP2013, as I myself have only encountered this in SP2013. My personal explanation to this: SharePoint 2013 Content By Query web part has a minor bug in its early releases. When returning no items it accidentally breaks the HTML structure of the page. My solution: Open the ContentQueryMain.xsl in SharePoint Designer. Find the XSL ...


4

You'll need to use an additional XSL schema called ddwrt. Here is a blog with a good and simple walk-through <xsl:value-of select="@ArticleStartDate"/> You get back a pretty nasty looking result 2009-03-23 00:00:00 However if you use the “FormatDate” function, you can make this look a lot better. <xsl:value-of ...


3

The CQWP cannot support this. You can connect to the other web applications using SharePoint designer and talk to SharePoint using web services (or RSS). However, I do am not aware of whether that limits you to a single list or cross-list. The list of web services is available on MSDN. Alternatively look at the Lightning Conductor webpart from Lightning ...


3

You need a custom web part that impersonates an authorized user to retrieve the metatdata of the prohibited lists. My first thought was that you could give users access to the lists and use information rights management to stop them viewing the documents, or give them view but not open permissions, but that really only stops a user accidentally viewing the ...


3

I'm not sure, but I'm pretty sure that the Managed Metadata column is sort of like the Multiple Choice column type - that it can store multiple values, and thus can't be filtered in the CQWP. (If you think about it, the database query would have to match on only part of the value that's serialized into the database field, and hence it would be REALLY slow) ...


3

A DVWP is going to be the way to go. When you set to DataSourceMode="CrossList", you can get at all of the items in lists that meet the criteria you set. Performance is usually not a problem, in my experience, unless you're dealing with multiple "large lists", which you say above isn't the case. Once you get the hang of doing a DVWP with CrossList mode, ...


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

Check out this article. It shows you how to replace the fields you want to render, using the "fields to display" section. Another article from MSDN here and here.


3

In 2007, when you select a coulmn to filter on that is a person/group field, there is an option to filter by Me. This works the same as any regular list/library where you have views filtered by the current logged in user. The CQWP works the same way. I assume there is something similar in 2010, I don't have a farm to view that in specficly at this time.


3

The CQWP layout can be changed to your needs by customizing the xsl the webpart uses. An explanation can be found here: http://msdn.microsoft.com/en-us/library/bb447557.aspx Some more background info can be found here: http://blogs.msdn.com/b/ecm/archive/2010/05/14/what-s-new-with-the-content-query-web-part.aspx


3

Just add the anchor tag with a dynamic link to the bottom of your itemstyle xsl and then wrap it with an xsl:if statement to check the position to see if the last list item is last. <xsl:if test="position() =last()"> <a href="link.aspx">View all items</a> </xsl:if> If you want to make the href dynamic, find a source for the link ...


3

It migth be more efficient to use Camlex.NET. It more understandable for new to SharePoint developers. Stramit SharePoint Caml Viewer migth be helpfull if you tried to write caml by hands, nor using UI or C# code.


3

This is not a CSS issue. I don't know how to fix it properly, but I can add this information: Issue occurs in IE 9 with hardware acceleration turned on for any SharePoint 2010 page with a content query web part added. Affects SharePoint menus (Site Actions) and some other forms of drop-down menu add ins. The reason the IE7 mode etc. works, you're then ...


3

About Social Comments In comparison to page fields (Page Content, Title, Page Image and etc.) that are inserted into the “slots” of the page layout and associated with the content type of the publishing page, social comments are stored separately. Social comments are stored in separate DB and the comment entry is associated by the page Url on which ...


3

See if this helps: <xsl:for-each select="rows\row"> <li> <a> <xsl:attribute name="href"> <xsl:value-of select="{@FileURL}" /> </xsl:attribute> <xsl:attribute ...


3

I was able to do it by modifying the ContentQueryMain.xsl file to insert non-repeating markup before and after content query as shown here. http://blog.mastykarz.nl/wrapping-contents-content-query-web-part-additional-markup/


2

Rather than indicating where the documents should be displayed, create columns for the document that indicate what the documents are (Content Types) or about (metadata). Then your pages can display things based on the characteristics of the document rather than where someone thought the document should go. This is a better answer for many, many reasons, ...


2

You will probably need to edit the xsl to add a disable-output-escaping attribute. http://blogs.msdn.com/ben_hickman/archive/2009/05/22/content-query-web-part-example.aspx


2

Could you use a DVWP (Data View Web Part) to display the data and then create a linked data source from your top level site and the relevant project site in SharePoint Designer? More info on creating linked/merged data sources here: http://office.microsoft.com/en-us/sharepointdesigner/HA101154041033.aspx I guess the downside here is going to be maintaining ...


2

Can you check the below article and see if this solves your problem http://platinumdogs.wordpress.com/2010/03/03/sharepoint-referencing-the-current-site-url-in-a-data-view-web-part/


2

Managed metadata columns can be used in the CQWP till they are not selected to allow multiple values when you define then under site columns. Once you have selected them to allow multiple values , CQWP will treat them as a Mulitple Choice column type and will not display them under the Allowed Columns dropdown...


2

You can alter the OuterTemplate.Empty XSLT template in the ContentQueryMain.xsl file. This template displays a message only when the web part is in edit mode but you can modify the XSL to display it even when it is in run-mode. Check this out: ...


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 ...



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