Qlik Community

Ask a Question

New to Qlik Sense

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

Announcements
Our May 2021 end-to-end product release from Data Integration to Data Analytics is out! READ DETAILS
cancel
Showing results for 
Search instead for 
Did you mean: 
markella92
Contributor
Contributor

how exclude records that matches between two tables

hi guys, how  can exclude records that matches between two tables in QlikSense with LOAD statement?

I post pic SQL side, i need QlikSense side.

Thanks

Labels (2)
1 Solution

Accepted Solutions
marcus_sommer
MVP & Luminary
MVP & Luminary

It could be done with an exists-clause like:

load * from Salary;

load * from Employee where not exists(ID);

- Marcus

View solution in original post

5 Replies
marcus_sommer
MVP & Luminary
MVP & Luminary

It could be done with an exists-clause like:

load * from Salary;

load * from Employee where not exists(ID);

- Marcus

View solution in original post

markella92
Contributor
Contributor
Author

without inner join?
marcus_sommer
MVP & Luminary
MVP & Luminary

To check the existence of fieldvalues within a load against already loaded fieldvalues of this field is no join necessary. Depending on your requirements you might need to adjust the load-order and/or to rename fields because exists() checks the values against the symbol-table and not against the data-tables but even then it's often easier to handle as joining-approaches.

On the bottom of the following post you will find several examples and explanations for the use of exists especially in scenarios which needs to keep qvd-loadings optimized: Advanced-topics-for-creating-a-qlik-datamodel.

- Marcus

markella92
Contributor
Contributor
Author

can i pass more than 2 fields to function not Exists()?
marcus_sommer
MVP & Luminary
MVP & Luminary

You might use multiple exists() like:

where exists(Field1) and exists(Field2);

or maybe using exists() with a second expression-parameter like:

where exists(KEY, ID & '|' & YearMonth);

whereby both approaches will result in unoptimized loads but this mustn't be a showstopper if the dataset isn't too large.

- Marcus