Tag Info

New answers tagged

0

You'd want to wrap that in an if, something along the lines of this: <xsl:if test="string-length(@MyDesc) &gt; 400"> <xsl:value-of disable-output-escaping="yes" select="substring(@MyDesc,1,400)" /> - <a href="{$SafeLinkUrl}">[Full Announcement]</a><br /> </xsl:if>


0

Create new style in ItemStyle.xsl xsl:template name="MyNewStyleName" match="Row[@Style='LoanerRequestCustomStyleTwo']" mode="itemstyle" /xsl:templet In ContentQueryMain.xsl In " xsl:template name="OuterTemplate.CallHeaderTemplate"> " Tag Search for xsl:value-of disable-output-escaping="yes" select="$BeginListItem" / Usually can be found on ...


0

In my experience, the column will have to be created as a site column to show up in a CQWP. If you created the column in the document library only, it will not show up as a filterable column.


1

I have a list MyTestList. It has currently two views TestView1 and TestView2. To add serial number in the front follow the following steps: Open the site in SPD Open the List Edit the view in Split mode Select the List, Go to 'List View Tools' in the Ribbon > 'Design' > 'Customize XSLT' > 'Customize Entire View' This will convert the view in detail xslt ...


1

You can use SPD. On a page add the list view, then create a column and insert the following code: <xsl:value-of select="count($thisNode/../*[not($thisNode/@ID=preceding-sibling::*/@ID)])" /> It should render the row number, no matter if you change the view order or filter some information. Hope this helps


0

The CQWP has its own internal caching that can be modified by exporting the web part and editing the DWP file. I think it caches results for 15min. Other then this, the only thing I can think of is that there may be security issues on the itmes (i.e. current user does not have read access to them) or filter settings that are preventing these values from ...


0

To achieve the output of all comment versions I found a solution on Marc D Anderson's Blog. In order to get this to work I had to switch from using a CQWP to a DVWP, but this wasn't a struggle. For those looking for a quick copy and paste the following was used within the xslt: <SharePoint:AppendOnlyHistory FieldName="Comments" runat="server" ...


0

if the list contains less than 5000 items, the performance of the CQWP is likely to be very good. However, if the list exceeds 5000 items, and the query in the CQWP is complex, the Web Part can run into performance problems. It’s difficult to define exactly what a complex query is, but a Source that goes across all sites in your site collection is more ...



Top 50 recent answers are included