https://community.qlik.com/t5/Talend-Studio/Get-nodes-not-just-strings-in-tFileInputMSXML/m-p/2201776#M3730 Is there a way in the tFileInputMSXML component to retrieve nodes, i.e. whole subtrees, in a column of type Document?<BR />I have a large XML file that is not only multi-schema, but also nested in multiple (=4-5) levels. I got tFileInputMSXML running to loop at any required nesting level and parse all the schemata I want. However, I have 100-200 schemata I need to parse altogether, so parsing them with a single tFileInputMSXML component seems not to be a good idea in terms of job design.<BR />Therefore, I would like to parse upper nodes into their corresponding schemata, while preserving their child nodes as Documents. This way, I can delay the processing of the child nodes into subsequent components like tExtractXMLField and thus handle complexity by not having to parse all of the 100-200 different schemata at once inside a single tFileInputMSXML component.<BR />What can I do?<BR />What I have tried so far:<BR />1. The tutorial (<A href="https://help.talend.com/search/all?query=tFileInputMSXML&amp;content-lang=en" target="_blank" rel="nofollow noopener noreferrer">https://help.talend.com/search/all?query=tFileInputMSXML&amp;content-lang=en</A>) selects a node with multiple children, but only outputs them as a string (see my comment at the bottom of the page).<BR />2. The (non-multischema) tFileInputXML component has a "Get nodes" option for this case, but the tFileInputMSXML component has not. Tue, 03 Dec 2013 11:09:13 GMT Anonymous 2013-12-03T11:09:13Z https://community.qlik.com/t5/Talend-Studio/Get-nodes-not-just-strings-in-tFileInputMSXML/m-p/2201776#M3730 Is there a way in the tFileInputMSXML component to retrieve nodes, i.e. whole subtrees, in a column of type Document?<BR />I have a large XML file that is not only multi-schema, but also nested in multiple (=4-5) levels. I got tFileInputMSXML running to loop at any required nesting level and parse all the schemata I want. However, I have 100-200 schemata I need to parse altogether, so parsing them with a single tFileInputMSXML component seems not to be a good idea in terms of job design.<BR />Therefore, I would like to parse upper nodes into their corresponding schemata, while preserving their child nodes as Documents. This way, I can delay the processing of the child nodes into subsequent components like tExtractXMLField and thus handle complexity by not having to parse all of the 100-200 different schemata at once inside a single tFileInputMSXML component.<BR />What can I do?<BR />What I have tried so far:<BR />1. The tutorial (<A href="https://help.talend.com/search/all?query=tFileInputMSXML&amp;content-lang=en" target="_blank" rel="nofollow noopener noreferrer">https://help.talend.com/search/all?query=tFileInputMSXML&amp;content-lang=en</A>) selects a node with multiple children, but only outputs them as a string (see my comment at the bottom of the page).<BR />2. The (non-multischema) tFileInputXML component has a "Get nodes" option for this case, but the tFileInputMSXML component has not. Tue, 03 Dec 2013 11:09:13 GMT https://community.qlik.com/t5/Talend-Studio/Get-nodes-not-just-strings-in-tFileInputMSXML/m-p/2201776#M3730 Anonymous 2013-12-03T11:09:13Z https://community.qlik.com/t5/Talend-Studio/Get-nodes-not-just-strings-in-tFileInputMSXML/m-p/2201777#M3731 Hi, <BR />What is the structure of your document? Is it possible to paste it on forum?<BR />Best regards<BR />Sabrina Wed, 04 Dec 2013 04:00:41 GMT https://community.qlik.com/t5/Talend-Studio/Get-nodes-not-just-strings-in-tFileInputMSXML/m-p/2201777#M3731 Anonymous 2013-12-04T04:00:41Z