Cross-posted from EndUserSharePoint.com… <xsl:param> A value you’ve passed into a template with <xsl:with-param>. You need to have an <xsl:param> at the top of the template for each value you expect to be passed into it. I talked in the last post about passing values into templates using <xsl:with-param>. Whenever you pass these values, you need…
Cross-posted from EndUserSharePoint.com… <xsl:with-param> You use this with <xsl:call-template> when you want to pass a value into a template, usually a value that varies. Once you’ve laid down the foundation and framed the rooms with <xsl:template> and <xsl:call-template> (one of my goals in this series is to mix as many metaphors as possible), you can…
Cross-posted from EndUserSharePoint.com… <xsl:call-template> This is how you call a template which you’ve defined with <xsl-template>. In the last installment, I showed you what templates SharePoint Designer usually creates when you set up a Data View Web Part (DVWP). Having the templates in place is great, but you need a way to chain them together…
Cross-posted from EndUserSharePoint.com… <xsl:template> Think of a template as a subroutine. It’s a unit of XSL to which you pass control. A template in a Data View Web Part’s (DVWP’s) XSL is a really important “unit of measure”. When you first drop a DVWP on the page and configure it, SharePoint Designer will automagically create…
Cross-posted from EndUserSharePoint.com… Data View Web Parts (DVWPs) are, to me, the most powerful feature in SharePoint. You’ve probably heard them called the Swiss Army Knife of SharePoint and there’s really very little that you can’t display with them if you understand how they work. But understanding the inner working of DVWPs requires knowledge of…