Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 715777
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 14, 20262026-05-14T05:13:31+00:00 2026-05-14T05:13:31+00:00

I’m working with an OpenXML document, processing the main document part with some XSLT.

  • 0

I’m working with an OpenXML document, processing the main document part with some XSLT.

I’ve selected a set of nodes via

<xsl:template match="w:sdt">
</xsl:template>

In most cases, I simply need to replace that matched node with something else, and that works fine.

BUT, in some cases, I need to replace not the w:sdt node that matched, but the closest w:p ancestor node (ie the first paragraph node that contains the sdt node).

The trick is that the condition used to decide one or the other is based on data derived from the attributes of the sdt node, so I can’t use a typical xslt xpath filter.

I’m trying to do something like this

<xsl:template match="w:sdt">
  <xsl:choose>
    <xsl:when test={first condition}> 
        {apply whatever templating is necessary}
    </xsl:when> 
    <xsl:when test={exception condition}> 
      <!-- select the parent of the ancestor w:p nodes and apply the appropriate templates -->
      <xsl:apply-templates select="(ancestor::w:p)/.." mode="backout" />
    </xsl:when> 
  </xsl:choose> 
</xsl:template>


<!-- by using "mode", only this template will be applied to those matching nodes
     from the apply-templates above -->
<xsl:template match="node()" mode="backout">
  {CUSTOM FORMAT the node appropriately}
</xsl:template>

This whole concept works, BUT no matter what I’ve tried, It always applies the formatting from the CUSTOM FORMAT template to the w:p node, NOT it’s parent node.

It’s almost as if you can’t reference a parent from a matching node. And maybe you can’t, but I haven’t found any docs that say you can’t

Any ideas?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-14T05:13:31+00:00Added an answer on May 14, 2026 at 5:13 am

    This:

    <xsl:apply-templates select="(ancestor::w:p)/.." mode="backout" />
    

    will find all w:p elements that are ancestors of the context node, and apply templates to the parent elements of each. It sounds to me like maybe what you want to do is find only the nearest ancestor, e.g.:

    <xsl:apply-templates select="ancestor::w:p[1]/.." mode="backout" />
    

    But what you’re describing here should be working, in some fashion. You should probably verify that what you think is happening is actually what’s happening, by replacing your backout template with something more diagnostic, e.g.:

    <xsl:template match="node()" mode="backout">
       <xsl:text>backout matched a </xsl:text>
       <xsl:value-of select="name()"/>
       <xsl:text> element.</xsl:text>
    </xsl:template>
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Ask A Question

Stats

  • Questions 385k
  • Answers 385k
  • Best Answers 0
  • User 1
  • Popular
  • Answers
  • Editorial Team

    How to approach applying for a job at a company ...

    • 7 Answers
  • Editorial Team

    How to handle personal stress caused by utterly incompetent and ...

    • 5 Answers
  • Editorial Team

    What is a programmer’s life like?

    • 5 Answers
  • Editorial Team
    Editorial Team added an answer It's giving you errors because the constructor has required parameters.… May 14, 2026 at 11:36 pm
  • Editorial Team
    Editorial Team added an answer According to the reference, SET fields use one byte minimum… May 14, 2026 at 11:36 pm
  • Editorial Team
    Editorial Team added an answer Dreamweaver is mostly a waste of money unless the site… May 14, 2026 at 11:36 pm

Trending Tags

analytics british company computer developers django employee employer english facebook french google interview javascript language life php programmer programs salary

Top Members

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.