# Create XML Node fails

**URL:** https://www.finalbuilder.com/forums/t/create-xml-node-fails/3408
**Category:** Bugs
**Created:** [November 24, 2011, 11:43am UTC](https://www.finalbuilder.com/forums/t/create-xml-node-fails/3408 "2011-11-24T11:43:20Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![michael.jelich](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/m/c57346/32.png) [@michael.jelich](https://www.finalbuilder.com/forums/u/michael.jelich)
#### Post date: [November 24, 2011, 11:43am UTC](https://www.finalbuilder.com/forums/t/create-xml-node-fails/3408/1 "2011-11-24T11:43:20Z")

</div>

Hi support team,

I want to create a manifest file by means of FinalBuilder. For this I&nbsp;create an empty xml file and add the following line:

This node is added by this&nbsp;child node:

The XPATH&nbsp;expression "/a:assembly/b:trustInfo" fails unless I&nbsp;save and reopen the XML&nbsp;file.

Attached you'll find a sample project showing this behavior.

I&nbsp;don't know whether or not it is a bug or my fault.

Can you help?

Best regards

Michael

[20111124\_CreateManifest.fbp7](https://www.finalbuilder.com/forums/uploads/default/original/2X/2/2e15d41679ddef40cc032b891115c36f7eed25f2.fbp7) (119.365 KB)

---

<div class="post-metadata">

### Author: ![stephen.ryan](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/s/f14d63/32.png) [@stephen.ryan](https://www.finalbuilder.com/forums/u/stephen.ryan)
#### Post date: [November 25, 2011, 2:06am UTC](https://www.finalbuilder.com/forums/t/create-xml-node-fails/3408/2 "2011-11-25T02:06:01Z")

</div>

Hi Michael   
  
 I have had a look at your example, I believe you are seeing this error because even though you have defined the namespace prefixes when you are creating the document, the namespace cannot be resolved because the namespace you are referencing does not exist in the document at this point in time.   
  
 If I insert the the ‘trustInfo’ node into the initial document definition (and disable the action that inserts this node) then the project works as expected, as the namespace is present and can be resolved when the document is defined.   
  
 You have a couple of options:   
  
 1. Include any nodes that define namespaces into the initial document definition, so that the namespace prefixes can be resolved.   
 2. Save the document after the initial definition, then when adding the new nodes (step 2 in your example script) reference the file itself, rather than the XML document. This will allow you to set the MSXML parser options for each operations, allowing you to reference and alias new namespaces as they are added.   
  
 Hope this helps.   
  
 Regards,   
 Steve