Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Join us to spark ideas for how to put the latest capabilities into action. Register here!
cancel
Showing results for 
Search instead for 
Did you mean: 
francisvandergr
Partner - Creator II
Partner - Creator II

Concatenate on resident table

I have a question. Script below doesn't work. I have a table what is called Sales. In the second part of the script i wanna load only records (FACTUUROPDRACHT) which are not in the first part of the script. The problem is that i see no records from the second part. Do anyone know a reason ?

Sales:
LOAD FACTUUROPDRACHT,
    CDDEBITEUR,
    OPDRACHTDATUM,
    CDARTIKEL,
    OMSCHR,
    DATUM,
    '1' as Part

Resident Factuuropdracht60100  WHERE CDARTIKEL='60.100'  ORDER BY FACTUUROPDRACHT;
drop table Factuuropdracht60100;


Concatenate load
    FACTUUROPDRACHT,
    CDDEBITEUR,
    OPDRACHTDATUM,
    CDARTIKEL,
    OMSCHR,
    DATUM,
     '2' as Part

Resident Factuuropdracht60300 where not exists (FACTUUROPDRACHT);
drop table Factuuropdracht60300;

3 Replies
prieper
Master II
Master II

Hmmm: script seem to be o.k. I always tend to specify JOIN- or CONCATENATE-commands, so try with CONCATENATE (Sales) LOAD ....

If the Factuuropdracht60300-table has the same format, the script will concatenate to this table and will be deleted.

HTH
Peter

nagaiank
Specialist III
Specialist III

Try the following and see if it works.

Sales:

NoConcatenate
LOAD FACTUUROPDRACHT,
    CDDEBITEUR,
    OPDRACHTDATUM,
    CDARTIKEL,
    OMSCHR,
    DATUM,
    '1' as Part

Resident Factuuropdracht60100  WHERE CDARTIKEL='60.100'  ORDER BY FACTUUROPDRACHT;
drop table Factuuropdracht60100;


Concatenate load
    FACTUUROPDRACHT,
    CDDEBITEUR,
    OPDRACHTDATUM,
    CDARTIKEL,
    OMSCHR,
    DATUM,
     '2' as Part

Resident Factuuropdracht60300 where not exists (FACTUUROPDRACHT);
drop table Factuuropdracht60300;

Not applicable

Krishnamoorthy is right. QlikView is automatically concatenating the tables because all the fields are named the same.