New answers tagged xslt
0
Did it a bit differently and finally it works, code if anybody had similar problem:
<xsl:template match="FieldRef[(@Encoded) and @Name='MyCustomColumn']" priority="10" ddwrt:dvt_mode="body" mode="Lookup_body" ddwrt:ghost="" xmlns:ddwrt2="urn:frontpage:internal">
<xsl:param name="thisNode" select="."/>
<xsl:if ...
0
with the use of your code, I was finally able to produce the formatting results I wanted. Below is the XSL I used:
<xsl:for-each select="All_Results/Result">
<xsl:if test="position() mod 2 = 1">
<div style="width:50%;float:left;"><xsl:call-template name="SingleResult"/></div>
</xsl:if>
...
1
I can't recall if the People Search XSL contains a Current Position parameter. But if it does, XSL has a method called mod which is commonly used to alternate item display.
Example:
...
<xsl:if test="position() mod 2 = 0">
<!-- Your HTML for items -->
</xsl:if>
<xsl:if test="position() mod 2 = 1">
<!-- Your HTML for ...
1
High level steps for an InfoPath browser form:
You don't need any fields in the main data source, but you need a secondary data source to the list, including all the fields you want to show in the form.
You will need code to get a URL parameter into the InfoPath form. There is a plug-in for InfoPath from Qdabra Software called "qRules" that loads DLL's ...
0
You use the following format, you are pretty close.
<xsl:value-of select="@Resources.resourceFile.ResourceName" />
is
<xsl:value-of select="@Resources.custom.custome_resource" />
will get custom.wss and custom_resource inside it.
0
Your nearly there its just the syntax of the parameter filter.
Try:-
<xsl:variable name="Rows" select="/dsQueryResponse/Rows/Row[ActiveStatus='Yes']"/>
There are some good examples in this MSDN article.
http://msdn.microsoft.com/en-us/library/ms950787.aspx
0
Yes you can do this with XSL and CAML. I have done similar to create a Risk Matrix which is detailed on my blog. You will have to adjust the concept to meet your own requirements but it should hopefully point you in the right direction.
Depending on what you want to achieve you could also create a basic bar chart in the XSL sizing SPAN objects based on ...
0
When you "Customise entire view" you will notice you suddenly have 4,000 extra lines of code as the XSLT that SharePoint generates is trying to cover lots of eventualities. However, I have not experienced a delay in the range you are suggesting, particularly for such a small data set.
Have you tried setting "Customise entire view" but then not making any ...
0
I think I have found a solution. I made a page that takes the sub-element as a query-string parameter. It then renders the web-parts that it needs. Then in the main page, in the XSLT, for each row I use an iframe while passing the sub-element as a query-string. I call the su-element page in the iframe.
So I am not trying to use webparts in the XSLT, but I ...
0
Data View Web Parts are very good at filtering data from lists and translating the XML to client side code like HTML or Javascript. However, I don't think a web part is a good target output, because that is normally processed on the server side. Instead, I would look at connecting the DVWP to the other web parts on the page and providing the values from the ...
1
If you insert the default CQWP throught the UI it will automatically use the ItemStyle.xsl from the Style Library by default.
In order to do what you want to do, you'd have to create your own CQWP and add some EditorPart or Toolpart to it in which you include the functionality to be able to choose whatever XSLT file for itemstyles you want.
Here's an ...
0
Try this:
ddwrt:FormatDate(string($item_date) ,1038 ,1)
I am using this to format date to dd.mm.yyyy format.
Top 50 recent answers are included
