Databases
StackOverflow2013
Postsdbo
POUnusual XML notations of mergefields in DOCX file.
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POUnusual XML notations of mergefields in DOCX file.
    primarykey
    data
    text
    <p>In our document generation system we use DOCX files in which we programmatically fill out mergefields. For this I'm using the OpenXml SDK 2.0. </p> <p>I've been plowing through the document.xml file, in de docx, and found that the mergefields are usually represented by a SimpleField. An example from a document we use: </p> <pre><code>&lt;w:fldSimple w:instr=" MERGEFIELD NP021_INSSNumber \* MERGEFORMAT "&gt;&lt;w:r&gt;&lt;w:rPr&gt;&lt;w:noProof/&gt;&lt;/w:rPr&gt;&lt;w:t&gt;«NP021_INSSNumber»&lt;/w:t&gt;&lt;/w:r&gt;&lt;/w:fldSimple&gt; </code></pre> <p>A fairly straightforward notation, containing the mergefield command and the text to be displayed in the document. It's fairly easy to find this tag in the XML, just search for w:fldSimple tags. (I removed some style tags to make it more readable)</p> <p>But a document recently created in Word didn't parse in our code, and when I looked in the XML the notation for mergefields was completely different: </p> <pre><code>&lt;w:instrText xml:space="preserve"&gt; MERGEFIELD NP021_INSSNumber \* MERGEFORMAT &lt;/w:instrText&gt; </code></pre> <p>And later in the document I found the display notation: <code>&lt;w:t&gt;«NP021_INSSNumber»&lt;/w:t&gt;</code> This is spectacularly impossible to parse in code. </p> <p>How is it possible that doing the same thing in Word can have such different results, and is there a way to ensure that Word uses SimpleFields as XML notation for mergefields?</p> <p>Thank you in advance for any helpful input.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USJoachim VR
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POUnusual XML notations of mergefields in DOCX file.
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI am seeing the same issue and trying the RevisionAcceptor and simplifying markup doesnt fix it. My merge fields are still staying as a instrText and not being converted back to fldSimple. Has anyone else seen this before? How did you resolve this issue?
      singulars
      1. POUnusual XML notations of mergefields in DOCX file.
      1. USLav
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload