Get XMl data

Help
1

hello.

I need to get an information inside a XML file.

I did that:

image
image1111×497 93 KB

i need to get the number in the field “chave”

Thanks

2

@brunobufolo

As per the message box, you’re trying to get the count of “Chave”. Can you please remove count and try only with xmlout.Descendants(“Chave”).ToString.

3

@singhonkar
this messsage appear:

image

4

Hi,

As per the message you get the list of nodes not the value
Can you try like xmlout.descendants(“”)(0). value

5

@brunobufolo

Could you please try once with xmlout.Descendants(“chave”).Value.ToString.

Let me know if this works or not.

6

@venkat4u @singhonkar

I used this code: xmlout.Descendants(“chave”).value

and this message appear:
image

If i use this: xmlout.Descendants(“chave”).value.tostring

this message appear

image

7

Can you share your xml file

8

@brunobufolo

Sorry for the late reply. Can you please try the below command in the your message box and let me know if this works or not.

xmlout.Element(“cteProc”).Element(“CT e”).Element(“infCte”).Element(“infCT eNorm”).Element(“infDoc”).Element(“infNFe”).Element(“chave”).Value.ToString

Please cross check all of these tags names as screenshot resolution is not good.

9

hello, @singhonkar and @venkat4u

For this code: xmlout.Element(“cteProc”).Element(“CT e”).Element(“infCte”).Element(“infCT eNorm”).Element(“infDoc”).Element(“infNFe”).Element(“chave”).Value.ToString

this message appear:

image
image1440×900 126 KB

In attach I left the XML file:
35190343500198000185570000003091261327667357.xml (7.5 KB)

thanks!

10

@brunobufolo

Please try once with ExecuteXPath activity as the data which you want to retrieve is in nested state.

Refer to this post: Fetch XML node value (with condition on other node values) using Execute Xpath utility in UIPath - #14

11

hello @singhonkar and @venkat4u

i tried this:

image
image490×594 15.5 KB

and this messsage appear:
image

sorry for my late to answer…

12

Hello,

This is due to the lack of specifying a namespace prefix in the source XML as such, when using XPath or traversing the DOM it doesn’t know how to reference the elements as the default namespace has no prefix.

Note: This is not specific to UiPath, but difference applications and languages deal with it in different ways.

You have a couple of options and ways to work around this depending on the influence you have on the original source.

  1. Provide a prefix for the namespace from the source and prefixing the nodes with the prefix

      <CTe xmlns="http://www.portalfiscal.inf.br/cte">
    <infCte versao="3.00" Id="CTe35190343500198000185570000003091261327667357">
      <infCTeNorm>
        <infDoc>
...

    becomes

      <CTe xmlns:someprefix="http://www.portalfiscal.inf.br/cte">
    <someprefix:infCte versao="3.00" Id="CTe35190343500198000185570000003091261327667357">
      <someprefix:infCTeNorm>
        <someprefix:infDoc>
...

  2. Strip/Replace the xmlns pseudo-attribute from each of the elements where needed using String.Replace or Regex/Regex.Replace. Deserialize the XML and query with XMLDocument methods or XPath as needed.

  3. Use the local-name / namespace-uri references when building your XPath expression. IT can get a bit messy, but it’s flexible without needing to modify the source XML.

    //*[local-name()='chave']

    Wrapping it in the fn:String() function and/or adjusting the query as needed.

  4. Register a NamespaceManager with the XmlDocument.NameTable for the defined namespace and provide a prefix to apply to the default space and use the XmlDocument or XDocument methods like you normally would turning the XPath query into something like

    //myprefix:chave

    For what little I’ve spent in this realm, this usually seems to be the correct approach (assuming you can’t influence the original source) to handling the default namespace with no prefix. I find it a bit cumbersome in UiPath and easier to go about it programmatically, so you’d probably find one of the other options easier and faster to work with.

I would recommend reading up more on XML Namespaces and XPath should you want to have a better understanding.

1 Like