Reading an XML file into an Interface

RE: Reading an XML file into an Interface

Acacio Barrado — Sat, 10 Apr 2021 01:09:55 GMT

Hi David,

The xml example that you provided is not a valid xml, the main problem is that you cannot have a XML tag name with spaces, otherwise the second word would be interpreted as an attribute.

I edited your example in order to make the XML valid, and from there you can adjust to your process. Please find the valid xml in the code below:

<?xml version="1.0" encoding="UTF-8"?>
<Root>
	<OriginalVariables>
		<CardholderElement>Carolina Kenny</CardholderElement>
		<CardNumberElement>449450294</CardNumberElement>
	</OriginalVariables>
	<Scanning/>
	<QueueInfo>
		<Company>Parkmill</Company>
	</QueueInfo>
</Root>

Below is the code example for you get the company value:

xpathdocument(
  docId: YOURDOC,
  expression: "Root/QueueInfo/Company/text()" 
)

In case these responses were helpful don't forget to mark the question as answered as it can also help other that are facing similar issues.

Regards,

Acacio B.

RE: Reading an XML file into an Interface

David Craven — Fri, 09 Apr 2021 08:52:04 GMT

HI Acacio

Your right - I got the first line of code to work within an expression rule, so Im just going wrong somewhere else in the process model.

Regarding the second method, that wouldn't work, although the structure of the XML file is slightly different - Ive tried replacing fields with Root and Original Variables - if you could let me know the correct syntax for it that would be great (Ive attached it here)

community.appian.com/.../Client_5F005F005F00_0001_5F00_GIRO_5F00_KTA.XML.xml

RE: Reading an XML file into an Interface

Acacio Barrado — Thu, 08 Apr 2021 22:46:03 GMT

Hey David,

For the XML that you post as example the first code that I sent in my previous answer should work, as I tested it in my local environment.

In order to speed up your tests you could upload a file to Appian and test it in an expression rule, just past the code that I sent and change the docId, in case it is working in the expression and failing in your process model you need to analyse in detail the steps in your PM.

Let me know,

Regards.

Acacio B.

RE: Reading an XML file into an Interface

David Craven — Thu, 08 Apr 2021 10:12:34 GMT

Just wondering - when I test the interface it is passing in the doc id and name into the rule input

BUt in the Process Model where it is passed into a parameter it is just the name

Would that be effecting it?

RE: Reading an XML file into an Interface

David Craven — Thu, 08 Apr 2021 10:10:51 GMT

Hi Acacio

Thanks for that. I've tried using both snippets of your code (replacing YOURDOC with pv!xmlFile, with each XML file but get the same error each time

Not sure where it is going wrong, have tried putting a tointeger() around the pv!xmlFile just in case

David

RE: Reading an XML file into an Interface

Acacio Barrado — Thu, 08 Apr 2021 00:06:52 GMT

Hi David,

Yes, there is a big difference in relation to the format of your XML.

In the current format as you sent in your example, the data that you are trying to retrieve is stored in one of the attributes from of the field called Field. This field is generated multiple times in your XML and the only difference between them is the values in the attributes (Field Name and value). It is possible to get the value that you are looking for, by AFAIK, you would need to rely on indexes, I’m attaching a code below where that you can use to get the Company value:

xpathdocument(
  docId: YOURDOC,
  expression: "Document/Fields/Field[2]/@Value" 
)

On the other hand, using the second format that you proposed you could easily get the value from company without need to rely on index. I’m attaching a code example below:

xpathdocument(
  docId: YOURDOC,
  expression: "Document/Fields/Company/text()" 
)

Regards

Acacio B.

RE: Reading an XML file into an Interface

David Craven — Wed, 07 Apr 2021 14:33:58 GMT

Ok thanks all

I've attached a copy of the sample XML I am using - dont think there is a namespace?

Currently the field data I am trying to grab from the XML is:

and this is the expression in the Process Model Script Task

=xpathdocument(
docID: pv!xmlFile,
expression: "/Document/Fields/Field[@Name='Company']/@Value"
)

Also, I just wondered what difference it would make if the XML fields were in the following format:

<Company>Parkmill</Company>

Would the expression need to be different?

community.appian.com/.../Sample-XML-1-_2D00_-General-Correspondence-CG-_2800_3_2900_.xml

RE: Reading an XML file into an Interface

Acacio Barrado — Wed, 07 Apr 2021 01:28:37 GMT

Hi David,

As pointed out by Mike, you don’t need to worry about the document Id, looking into the documentation for the function “xpathdocument”, we can see that the parameter docId is Any Type, and it would accept both, document or document Id. Therefore, there was nothing wrong in your implementation.

Documentation Reference:

docId (Any Type): Xml Document id or Content Item (Document).

About the name space, it is normally defined in the root node of the XML, it can be also defined direct in one of the XML nodes, so you need to check it in your XML file. An easy way to check is looking for prefixes in the child nodes or in the root node.

I’m adding a sample XML from w3schools, in it you will be able to see two name spaces with different prefix (h and f), so lets say that you want to return the child <f:name> under the node <f:table>, so you would need to add in the function parameter prefix, something like that:

prefix: "f:https://www.w3schools.com/furniture"

<root xmlns:h="http://www.w3.org/TR/html4/" xmlns:f="https://www.w3schools.com/furniture">
	<h:table>
		<h:tr>
			<h:td>Apples</h:td>
			<h:td>Bananas</h:td>
		</h:tr>
	</h:table>
	<f:table>
		<f:name>Coffee Table</f:name>
		<f:width>80</f:width>
		<f:length>120</f:length>
	</f:table>
</root>

I hope this helps you.

RE: Reading an XML file into an Interface

Acacio Barrado — Wed, 07 Apr 2021 01:26:11 GMT

Hi Mike,

I totally agree with you,

Thank you,

Acacio B.

RE: Reading an XML file into an Interface

Mike Schmitt — Tue, 06 Apr 2021 16:11:27 GMT

[quote userid="36529" url="~/discussions/f/process/20722/reading-an-xml-file-into-an-interface/80756#80756"]How would I find the DocumentID? [/quote]

Your assumptions are correct, as long as you account for needing to submit a form prior to accessing a document's properties (which i believe you're already doing correctly). If needed, you can always typecast a document object directly to its ID by, among other things, passing the document object through the "toInteger()" function. As I noted in my prior reply though, in almost all cases it won't make any difference, as integer and document objects will almost seamlessly cross-typecast as needed depending on the service in question.

RE: Reading an XML file into an Interface

Mike Schmitt — Tue, 06 Apr 2021 16:08:51 GMT

[quote userid="33453" url="~/discussions/f/process/20722/reading-an-xml-file-into-an-interface/80745#80745"]The input for the expression should be the document ID and not the document itself[/quote]

So just FYI... in almost all cases, there will be no difference, as the "document itself" (assuming you're referring to an object of type "Appian Document") is really just the document's ID, and use cases that require the ID will almost always typecast the document down to its integer ID if necessary.

RE: Reading an XML file into an Interface

David Craven — Tue, 06 Apr 2021 14:09:53 GMT

Hi Acacio

How would I find the DocumentID? This is my interface - I assume it is the 47259 stored in the rule input before the filename? What would be the best way of grabbing this in the process model?

Also, where do I check for if the xml has namespace?

This is the document properties of one I uploaded

Thanks
David

RE: Reading an XML file into an Interface

Acacio Barrado — Tue, 06 Apr 2021 03:40:11 GMT

Hi David,

Few recommendations that I could give to you:

The input for the expression should be the document ID and not the document itself
Check in your xml file if you have namespaces defined, in case you need, it needs to be a parameter in the expression
If you are trying to retrieve just the text out of one xml tag try to use “/text()” instead “/@value”

I’m adding a sample code below, in this example only the text of the tag "content" is retrieved:

xpathdocument(
  docId: 9999,
  expression: "/a:document/data/body/item/content/text()",
  /*sample namespace prefix just add if your input xml has ns*/
  prefix: "a:http://www.appian.com/ae/types/2009"
)

Regards,

Acacio Barrado.