Skip to main content
Woohoo! Qlik Community has won “Best in Class Community” in the 2024 Khoros Kudos awards!
Announcements
Join us at Qlik Connect for 3 magical days of learning, networking,and inspiration! REGISTER TODAY and save!
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

conditional load with filed from other table

hi,
is it possible to use a field from another (allready loaded) table in a load condition of another table ?
its possible in sql, but how could it be done in qlikview script ?

the table "customers" is loaded first.


"customers" (customer_id, customer_area, subarea_code, customer_name)

customer_area= city
subarea_code= district/zipcode

f.e. i want to load purchase histories from one table
"sales" (order_id, order_date, order_amount, item_ID, customer_id)


BUT only for customers who live in a certain area

of course this could be done in the document with listboxes etc. But the huge amount of data from orders should be limited during load.

i could  be usefull for other loads too, especiall with large amounts of data and distributed dependencies.

1 Solution

Accepted Solutions
datanibbler
Champion
Champion

Hi,

so you load a mastertable > customers < first?

You could do a restricted RESIDENT LOAD of that, restricting to the areas that you want (if you don't want all of them) and then use a WHERE EXISTS clause in the following LOAD of the > sales < table?

HTH

View solution in original post

2 Replies
datanibbler
Champion
Champion

Hi,

so you load a mastertable > customers < first?

You could do a restricted RESIDENT LOAD of that, restricting to the areas that you want (if you don't want all of them) and then use a WHERE EXISTS clause in the following LOAD of the > sales < table?

HTH

Not applicable
Author

yes, >customers< is loaded before >sales< . i edited the question to make that more clear.
your proposal worked well, thank you.

the load of the >customers< list will be restricted by area, containing only users that match the area.

other users needed to be loaded later on, f.e. with outer join load.the


i only used where not exists before for incremental loads
where NOT exists (change_date)

WHERE EXISTS (subarea_code) worked fine.