Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi community,
I'm struggeling with my data model where I tried to use Resident load
Initialload_TMP:
LOAD
ID,
NAME,
FIRST_NAME,
CHANGE_DATE
FROM [lib://Desktop/Incremental.xlsx]
(ooxml, embedded labels, table is MEMBERS);
Initialload:
load
ID,
NAME,
FIRST_NAME,
CHANGE_DATE
resident Initialload_TMP;
drop table Initialload_TMP;
I don't get any table created. What is the reason? I'd expect, that Initialload-table should be appeared.
Qlik automatically concatenates the tables that have all fields common. In your case since first and second tables have all same fields, they get concatenated to the first one, and you are dropping it, hence no table you get. What you can do is - use NoConcatenate, like:
Initialload_TMP:
LOAD
ID,
NAME,
FIRST_NAME,
CHANGE_DATE
FROM [lib://Desktop/Incremental.xlsx]
(ooxml, embedded labels, table is MEMBERS);
NoConcatenate
Initialload:
load
ID,
NAME,
FIRST_NAME,
CHANGE_DATE
resident Initialload_TMP;
drop table Initialload_TMP;
Qlik automatically concatenates the tables that have all fields common. In your case since first and second tables have all same fields, they get concatenated to the first one, and you are dropping it, hence no table you get. What you can do is - use NoConcatenate, like:
Initialload_TMP:
LOAD
ID,
NAME,
FIRST_NAME,
CHANGE_DATE
FROM [lib://Desktop/Incremental.xlsx]
(ooxml, embedded labels, table is MEMBERS);
NoConcatenate
Initialload:
load
ID,
NAME,
FIRST_NAME,
CHANGE_DATE
resident Initialload_TMP;
drop table Initialload_TMP;
The second table won't be created because the datastructure is the same like in your first table and therefore the data are just added to the first table which you afterward dropped. You could avoid it by adding any other field in the second load or using NOCONCATENATE as load-prefix.
- Marcus