Generate Xpath

[ppr (Peter Preuss)]

it’s about XML Namespaces which need to be handled

XML Extraction - Handling Namespaces (Tableau, Soap, OASIS types)

Going ahead Serializing the XML - output: xDoc | DataType: XDocument: [grafik] Checking if we have to handle XML namespaces [grafik] We do have: [grafik] Checking for some children: [grafik] Defining Namespace Variable [grafik] In some cases, we can also do: Assign Activity - xnsDefault = xDoc.Root.Name.Namespace Checkin the retrieval [grafik] xDoc.Descendants(xnsDefault + "productVersion") GetDescendants { [<productVersion build="456" xmlns="http://tableau.com/api">123</…

and for XPath we can use the namespace manager

Reading all the tags of an XML and take them to excel

@Fabian_DDD I do feel that a XPath Approach is better for the retrieval Setting up a NamespaceManager with a Config Datatable: [grafik] for the default namespace with empty prefix “def” is assigne as prefix the retrieval is configured as another datatable (could also be externalize into an excel) [grafik] I did also for a deeper nested element for demo purpose After all preperation it is iterating over the retrieval config and retrieves the specfied values. et voila: [grafik] So this …

in some cases, we can work with the local name only like

Execute xpath in studio

it was necessairy to fix the xml (some tags were not properly closed) Analysis: [grafik] so we do know which namespace we have to configure [grafik] and we can do the retrieval with the following options: [grafik] XPath: [grafik] or with the usage of a namespace manager currently I am working on a custom library (Reply XMLToolBox Activities) to dynamize it and making it more easy. But there are some XML specifics to handle as well. So we would recommend for XML Beginers to configure…