topic Re: Incremental Load is Not Working in QlikView

Incremental Load is Not Working

Anonymous — Wed, 03 Dec 2014 21:15:17 GMT

Hello,

I am using Qlik Sense and have the following script. But when I run the script, only the data from Incr_Invoices table (e.g. 10 records) are kept. None of the data from Invoices table (e.g. 1000 records) are brought into Incr_Invoices table (i.e. After the concatenation, Incr_Invoices table has 10 records). There are different InvoiceRecordID's in both tables.

I saw that there were some issues with "where not exists" command with QVD file created by Qlik Sense: http://community.qlik.com/thread/129921

Is this true? If so, is there an update to this issue?

Your advise is greatly appreciated!

Incr_Invoices:

LOAD *

FROM [lib://Spend/SPEND_DATA*.xlsx]

(ooxml, embedded labels, table is [08]);

Invoices:

NoConcatenate

Load *

from [lib://Spend/InvoicesBasic.qvd] (qvd) where 1=1;

Concatenate (Incr_Invoices)

Load *

Resident Invoices

where Not Exists(InvoiceRecordID);

Re: Incremental Load is Not Working

maxgro — Wed, 03 Dec 2014 21:32:12 GMT

Incr_Invoices:

LOAD *

FROM [lib://Spend/SPEND_DATA*.xlsx]

(ooxml, embedded labels, table is [08]);

Concatenate (Incr_Invoices)

Load *

from [lib://Spend/InvoicesBasic.qvd] (qvd)

where Not Exists(InvoiceRecordID);

Re: Incremental Load is Not Working

Anonymous — Thu, 04 Dec 2014 02:48:30 GMT

Massimo, thank you for your feedback. I tried the script, and all 10 records from InvoicesBasic.qvd got added to Incr_Invoices table.

This sounds like the behavior mentioned in the linked discussion topic mentioned above: http://community.qlik.com/thread/129921

"It seems as if in QlikSense the Where Exists is ignored and the whole QVD is loaded."

Do you or anyone else have additional suggestions?

Re: Incremental Load is Not Working

Anonymous — Thu, 04 Dec 2014 19:10:03 GMT

Hello all,

Is there a different method other than 'where not exists' to do incremental load?

Re: Incremental Load is Not Working

Anonymous — Tue, 01 Sep 2015 18:30:05 GMT

This issue is now fixed in Qlik Sense 2.0.2