LiveSite - XSLT component - Group of DCRs - XPath reference in component and XSL file

We are using group of DCRs for a component. We are getting silly issue and may be missing simple thing. The component is working if we put the XSLT code directly in the component. But it is not working(no error and for loop is not executing) when we put the same XSLT code in XSL file. Is there any different way of calling DCR groups in XSL file?

<Data>
  <Group ID="G01" Name="LeftNews">
    <Datum ID="D01-1" Type="DCR" Name="LDCR" Replicatable="true" CloneGroupID="id7vvyyx">
      DCR1 
    </Datum>
  </Group>
  <Group ID="G02" Name="MiddleNews">
    <Datum ID="D02-1" Type="DCR" Name="MDCR" Replicatable="true" CloneGroupID="id7vvyyz">
      DCR2 
    </Datum>
  </Group>
  <Group ID="G03" Name="RightNews">
    <Datum ID="D03-0" Type="DCR" Name="RDCR" Replicatable="true" CloneGroupID="id7vvyz1">
      DCR3
    </Datum>
  </Group>
</Data>

This is working when we put the below loop code directly in the componet.
<xsl:for-each select="Properties/Data/Group[@Name='LeftNews']/Datum[@Name='LDCR']/DCR/Root">


But if we keep this code in XSL file, it is not going in to the loop and not displaying any error.
The XSL file is rendering the other statements before this loop. But it is not going in to the loop.

No difference if we use Replicatable="true" to group or datum.

Windows, SitePublisher/LiveSite 7.3.2

Find more posts tagged with

Comments

Adam Stoller

check to make sure you only have the xml headers in one place - the textarea where you are including the xsl - or - the xsl file you are including - not both

Srinivasa Talla

The other div statements are displaying but not the code inside the loop.

Even I removed textarea element inside the loop, but still didn't see any change.

Garth McMillan

Just to be clear you're referencing an external XSL file in the component via something like <xsl:include href="http://www.interwoven.com/custom/path/to/file.xsl"/>?

I see you don't have a leading slash in your select statement ("Properties/Data/Group[@Name='LeftNews']/Datum[@Name='LDCR']/DCR/Root" instead of "/Properties/Data/Group[@Name='LeftNews']/Datum[@Name='LDCR']/DCR/Root"). The context when it gets to that for-each statement may not be the document root, meaning it will not match.

Srinivasa Talla

yes, it is used in XSL file as you said. Yes, that is the silly mistake. Thanks for your help.

But it should not work in component(directly pasting the same code) also, right? How it is working there without that slash?

Adam Stoller

My guess is that it would be a question of context - when you had it directly pasted in, the context was probably correct, but when you moved it into an included file, the context was no longer correct for the relative xpath specification.