PARTIAL LOAD works in 2 ways
The ADD statement in the load indicates to QlikView that it should add the additional rows
to the existing table. The REPLACE function will drop the existing table and replace it.
Whereas Incremental Load is completely about ADDING a new data, UPDATE the existing data and DELETING the existing data.
Partial load and Incremental load are two different concepts. As per my knowledge we cannot combine those.
Executes the current load script, including all script commands, such as
Drop Table and reloads data to the active QlikView document.
However, only those tables whose load and select statements are preceded
by the Replace or Add prefix are reloaded. Data
tables that are not affected by this kind of load or select statements will not
be affected by the partial reload.
It is defined as loading nothing but new or
changed records from the database. All other data should already be available, in one way or another. With
I know this topic is old, but I just wanted to point out that the replies you received are not correct.
You can deffinetly code a script where the "ADD Load" command only adds the new fields.
You could also implement a Keep function to define how to delete/update data.
Better late than ever
Not sure the Keep functions works the way you think it does.
The keep prefix is similar to the Join (page 250) prefix. Just as the join prefix, it compares the loaded table
with an existing named table or the last previously created data table.
But instead of joining the loaded table with an existing table, it has the effect of reducing one or both of the
two tables before they are stored in QlikView, based on the intersection of table data. The comparison made
is equivalent to a natural join made over all the common fields, i.e. the same way as in a corresponding join.
However, the two tables are not joined and will be kept in QlikView as two separately named tables.