LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

msxml property SelectSingleNode

Solved!
Go to solution

Hello,

 

I use the MSXML in labview to read a xml file. My VI works fine. But now I want to read the attribut xsi:noNamespaceSchemaLocation of the root node with the SelectSingleNode [queryString = @xsi:noNamespaceSchemaLocation] property. The result is an error. If I read all attributes of the root node, the VI doesnt show an error. Is it possible that labview or the property can't interpret the ' : ' (colon)? Because it can read every other attribut without a ' : '.

 

Thanks for answer,

shavo

0 Kudos
Message 1 of 4
(3,500 Views)

Hi shavo,

 

Good afternoon and I hope your well. I have noticed you have not currently received any support.

 

Are you still having trouble with the :?

 

I do not beleive the : should be an issue. However, if you could please post an example peice of code (and file) which generates this I would take a look at it for you. 

 

General advice,  make sure your using LabVIEW XML Schema and just double check the way your code handles the : string.

 

Thanks,

Kind Regards
James Hillman
Applications Engineer 2008 to 2009 National Instruments UK & Ireland
Loughborough University UK - 2006 to 2011
Remember Kudos those who help! 😉
0 Kudos
Message 2 of 4
(3,442 Views)
Solution
Accepted by topic author shavo

Hi Hillman,

 

thanks for your help, but I solved the problem on an other way. I used the property "attributes" > "nodeName". So I get an array of all attribute names and I compared it with the schema location attribut. Is there a match, the MSXML get the node value and it's all fine. I will create the next xml VI with the "selectsinglenode-colon-problem" and post it here.

 

See you soon 🙂

shavo

0 Kudos
Message 3 of 4
(3,439 Views)

Hi, I have the same problem with the colon.  If my xml schema has colons, and then I use the labview parsers to find nodes, I get an error.  When I remove the colons it works fine.  I see that there does not seem to be a resolution here.  Have either of you found anything since you originally posted this?  Maybe you need to use some special encoding of the colon when specifying the XPath Expression in the Get All Matched Nodes VI?

0 Kudos
Message 4 of 4
(2,787 Views)