topic Re: Resident load clarification in QlikView

Resident load clarification

Wed, 02 Sep 2015 15:37:22 GMT

I am trying to understand the resident load by using below link.Country table has 5 columns and calculation table has 2 columns.

Doubt:why in step 11[ Sheet property window] in above link is showing 5 columns instead of 6 columns.

Resident Load in QlikView

Re: Resident load clarification

Anonymous — Wed, 02 Sep 2015 17:48:01 GMT

Hi Vamsi,

Please elaborate on your query.

As per my understanding data is extracted from source is 5 columns and resident load is having two columns

([Country Name] and aggregation field).

[Country Name] field is common field between Country table( 5 columns) and Calculation table( 2 columns),so

they will be totally 6 columns.

Regards

Neetha

Re: Resident load clarification

maxgro — Wed, 02 Sep 2015 18:01:52 GMT

I think there are 6 fields because

- 5 fields from excel (Country table)

- 1 field (Calculation table, red arrow) from the new Calculation table loaded with the resident from Country table

Re: Resident load clarification

Wed, 02 Sep 2015 18:17:01 GMT

In sheet properties country name refers to which table (country table or calculation table).How qlikview will decide

Re: Resident load clarification

maxgro — Wed, 02 Sep 2015 18:28:45 GMT

both

the field is the field of all the tables

maybe an example can explain

Re: Resident load clarification

Wed, 02 Sep 2015 19:17:22 GMT

Hi Vamsi,

Country Name is acts like Connecting(Association) Column between two tables. Resident load means loading data from existing table.

If you see in Step 10, they extract Country name field again in [calculation table], that's why it appears with key symbol.

Re: Resident load clarification

Wed, 02 Sep 2015 19:59:21 GMT

qlikview will link tables together based on the same field name between the 2 tables. It is important to remember not to have multiple fields of the same name in more than one table - qlikview will always try to link tables based on column field names and if you have more than 1 common field name, you get a synthetic key relationship, which is something you do not want and should avoid

resident loads allows you to access a table (and then fields within the table) by accessing it within the system and not ahving to re-read the file in again (like it was originally read in)