You might be able to accomplish what you're trying to do with <xsl:number>
would have to see more of the code and source xml to be any help.

xsl isn't designed to be programmatic

12-01-2004T12:00:00 to only 12-01-2004
<xsl:value-of select="substring-before(., 'T')"/>

<?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:fo="http://www.w3.org/1999/XSL/Format"> <xsl:key name="Names" match="Name" use="."/> <xsl:templa...

getElementById("medicalid") This implies you're getting an element like so: <element id="medicalid"> I think you need to find a medical element where medical_field_id="PS" instead. Either change your source to use id attributes, or use getElementsByTagName("medical...

You can create 2 templates for the specified username nodes like so: <xsl:template match="userdetails/username"> <xsl:copy/> <!-- remove inside text --> </xsl:template> <xsl:template match="requestdetails/username"> <xsl:copy> <xsl:value-of select="//userdetails/username&quo...

Then afterwards, just use
<xsl:value-of select="//ACT"/>
or
<xsl:value-of select="SCHED//ACT"/>

Inside a SCHED context, eg, a <xsl:for-each select="SCHED"> or a <xsl:template match="SCHED">

<xsl:value-of select="count(ASSGN/ACT)"/>

<xsl:value-of select="count(//Flow[@From = $From])"/>

where $From is a parameter.

4 things here: 1. Key to match rows by parent. 2. Copy template for most nodes. 3. Seperate template for rs:data, so we can apply templates only to the top level rows. 4. Use of key in the z:row template The key is not necessary, but will speed things up if you have a lot of rows. <?xml version=&quo...

We'd need to see the rest of the javascript. Generally you'd pass in a parameter into the xslt, set up like: <xsl:stylesheet .... > <xsl:param name="start" select=""/> and then change your for-each loop to <xsl:for-each select="occupations/occupation[starts-with(description,...

Could you post the section of code where you are getting errors?

Not exactly sure if this is what you want.

<xsl:apply-templates select="//makeEdit | //make | //guardMake">
<xsl:sort select="@value"/>
</xsl:apply-templates>

<?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:fo="http://www.w3.org/1999/XSL/Format"> <xsl:template match="*"> <xsl:copy/> <xsl:apply-templates/> </xsl:template> ...

<?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:fo="http://www.w3.org/1999/XSL/Format"> <xsl:template match="include"> <xsl:copy-of select="document(@file)//*[...

instead, can you use:
dyn:evaluate
xmlns:dyn="http://exslt.org/dynamic"
?

Sorry I'm not of more help.

First, stop using /*/xml everywhere,-> this implies that you're using a xml node which is not the root (unless your input file is different than posted.) Second, unless you have multiple z:row 's in your xml in other locations, you can simply use z:row as the template match string. <xsl:template mat...

/*/*[2]

Does this xpath work?

It looks like the best solution for you is to post the xsl stylesheet to a globally available location.

If this same xml file is viewed many times, you might consider transforming the xml on the server itself before showing it to the user. Then the user only needs one access.

You could always do:
<xsl:variable name="qd">
<xsl:choose>
<xsl:when test="if(value/qDisplay/text() eq '')>empty</xsl:when>
<xsl:otherwise>right</xsl:otherwise>
</xsl:choose>
</xsl:variable>

Are you actually applying the template to this topicref node?
as in <xsl:apply-templates select="//topicref"/>

Entire condition should be in the brackets.. otherwise you're only taking one node, comparing to copiedItemRecKey, and then trying to count if it matched or not. moved the ']' <xsl:when test="(not(normalize-space(copiedItemRecKey) = '')) and (count(/SendRfqDto/scenariosToBeShopped//SpecialInqui...

Actually even more compact: This one represents more of what you're trying to do, copying everything, and editing only the Price. (wish they had edit post capability here) <?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform&...

<?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="2.0"> <xsl:output indent="yes"/> <xsl:template match="Root|Page|Story|Table"> <xsl:copy> <xsl:apply-templates/> </xsl:copy> </...

If it's always in the first cell in the row you could change to: <xsl:variable name="var" select="Cell/SKU[1]"/> If not always in the first cell in the row: <xsl:variable name="var" select="(Cell/SKU)[1]"/> Also in the corresponding price var I recommend using...

An element automatically falls under the same namespace as it's parent unless stated otherwise by declaring a different namespace. Additionally, if you wanted all elements in your output to have the same namespace you could move the xmlns attribute to your xsl:stylesheet element, eg. <xsl:stylesheet...

Just as a clarification You're using: <xsl:if test="not(@name=following::grp/@name)"> Which means if this is the last grp node in the FILE that has this name. Did you want the last node in the file, or did you want the first node, or maybe just the last node in this user? You may want (for...

You need to declare your namespaces in your xml file eg. <mh:MessageHeader> the xml has no idea what mh: represents. same with sn: eg you have in your schema file. xmlns:mh="http://mydomain.com/Namespaces/Container/Public/MessageHeader.xsd" xmlns:sn="http://mydomain.com/Namespaces/Con...

That sounds like they have started using a stricter format for URI.
Try using forward slashes / instead of backslashes \

I had the same problem when I went from Saxon 6 to Saxon 8 a couple years ago.

<xsl:template match="tocount">
<xsl:value-of select="1+count(preceding::tocount)"/>
</xsl:template>