This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- XMS replace and XPath problems
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 01, 2009
07:47 AM
XMS replace and XPath problems
Hi.
Im having trouble adding elements using the XML file changes in installshield.
I have defined the following node structure:
![](/legacyfs/online/vb/7985_ScreenShot001.jpg)
because I need to insert 12 Settings nodes under the Body node. This works fine for Settings[1] to Settings[9]. But Settings[10] and above nodes are not written to the XML file.
Is there a better way to do this or is there a bug in installshield? I checked the XPath standard and 10, 11, 12 seem to be valid and I even tested the XPath query in a visualizer.
Thanks
Rouan.
Im having trouble adding elements using the XML file changes in installshield.
I have defined the following node structure:
![](/legacyfs/online/vb/7985_ScreenShot001.jpg)
because I need to insert 12 Settings nodes under the Body node. This works fine for Settings[1] to Settings[9]. But Settings[10] and above nodes are not written to the XML file.
Is there a better way to do this or is there a bug in installshield? I checked the XPath standard and 10, 11, 12 seem to be valid and I even tested the XPath query in a visualizer.
Thanks
Rouan.
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 01, 2009
12:13 PM
As a guess, try inserting leading zeros on 1 through 9, making it 01 through 09. I suspect there may be some sort ordering causing this to work incorrectly without that.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 02, 2009
01:18 AM
Thanks.
Adding 0s in front fixed the problem.
Adding 0s in front fixed the problem.
![](/skins/images/8CE4FAD0DE6F3A6F9D0567434D2D2DAE/responsive_peak/images/icon_anonymous_message.png)