Qlik Community

New to Qlik Sense

If you’re new to Qlik Sense, start with this Discussion Board and get up-to-speed quickly.

Announcements
Customer & Partners, DEC. 9, 11 AM ET: Qlik Product & Strategy Roadmap Session: Data Analytics REGISTER NOW
cancel
Showing results for 
Search instead for 
Did you mean: 
spcon2016
Partner
Partner

Resident Load unexpected result

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.

Labels (1)
1 Solution

Accepted Solutions
tresesco
MVP
MVP

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;

View solution in original post

2 Replies
tresesco
MVP
MVP

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;

View solution in original post

marcus_sommer
MVP & Luminary
MVP & Luminary

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