New answers tagged xslt
If you're on SPD 2010, you can do this conveniently from the UI. Under List View Tools > Options > Parameters, create a new parameter, then add a filter which uses the newly created parameter. (In SPD 2013 it's similar, but getting the UI to show the List View Tools can be a bit trickier) You can do this manually too: add a ParameterBinding (the example is ...
I ran into this issue. The problem seems to be XSL transform caching. Specifically anonymous / vs authenticated users. An alternate solution is to add your xsl inline with the view. Just after the closing DataFields tag, add your XSL. </DataFields> <Xsl> <!– Add your custom xsl here –> </Xsl>
As you correctly noticed at least the repeating block could be refactored. For example, declare the following Xsl template for rendering Budget: <xsl:template name="RenderBudget"> <xsl:param name="CostCenter"/> <xsl:choose> <xsl:when test="$CostCenter = ''"> <span>0</span> ...
Have you validated the field is being pulled into your view by dropping it in an xsl:value-of select="@fieldname" You could also use identity transform as your xsl to validate the variable is coming through and the value. http://en.m.wikipedia.org/wiki/Identity_transform
Top 50 recent answers are included