This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
The Issue that your having is that each relation name is nested so the decision that you need to make is whether you are happy to just extract the information, or whether you need to parse the document.
If you need to parse the document, then an iterative macro will be best which basically runs an XML Parse tool on relation, until it can't fine relation name anymore.
If you are happy to just extract the data, then bring in the doc as csv with no delimiter. From there you have 2 options:
Thanks Kane , I need to bring it as XML File as I am also parsing other elements it it. I see that the delimeter option is when we specify alteryx that format is csv and give it with a delimeter option which might not work as ther other root and child elements might break.
I finally had a chance to take another look at this, it is not a full solution but I quickly put together an iterative Macro that removes the nesting in a pretty rough fashion. It should give you an idea of how to proceed.
Note: This Macro still uses some 'cheat' methods to align fields etc, that would be best made dynamic in production. In this kind of situation, the actual field names that get parsed are normally the same and so don't need to be made dynamic.
Thanks for your time and help, I have checked your macro and it definetly helps. But doesnt get the output in the desired way I was expecting
I just want to go and see if the Regex metho of just extracting the data will work out . I know you have extracted the relation name ,table and type earlier but just to add , I need the datasource name and caption added