Skip to main content
MAINTENANCE ALERT: Dec. 12th starting 9 AM CET. Community will be read-only. GET DETAILS
Showing results for 
Search instead for 
Did you mean: 
Partner - Contributor II
Partner - Contributor II

Load xml nodes as a unique field


Is there a way, when your script have to load an xml file, to create a field whose contents is a full node of the original xml file ?

Let's take a very simple example. Here is the xml source file body (find the file in attachement)

<?xml version="1.0" encoding="UTF-8"?>















If i use the wizard to load this file, Qlikview will generate 2 tables


LOAD code,


    %Key_student_C932B46F5721DF6D    // Key to parent table: student

FROM (XmlSimple, Table is [student/items/item]);


LOAD firstname,


    %Key_student_C932B46F5721DF6D    // Key for this table: student

FROM (XmlSimple, Table is [student]);

My Goal is to have only3 fields, one of them containing the all node "items". Something like that :


lastname items

Why that ? Because for the moment, I don't need any information about "items", but I want to collect this information and store it in my QVD, so that I will be able to parse it later if needed.

Have in mind that the node I want to store as it is is more complicated as in this example. It could contain other nodes which could contain other nodes... which would give me many tables linked each one to others, when I just need a way to store the information for later use.

Is there a way, or a trick, to get to that ?

Thanks for your help.


2 Replies

The easy way out is to simply store the item table to a qvd and drop it. When you need the data you can simply load the data from the qvd. It will be linked automatically using the Key_student_C932B46F5721DF6D field.

talk is cheap, supply exceeds demand
Partner - Contributor II
Partner - Contributor II

Thx, I agree, in my example, this could be the easiest way.

In my real case, it would not be one extra table to store as QVD, but many more, because of the structure of my xml node (tables in tables...), and as many QVD files to maintain on every update made by my collector...