Skip to main content
Announcements
NEW: Seamless Public Data Sharing with Qlik's New Anonymous Access Capability: TELL ME MORE!
cancel
Showing results for 
Search instead for 
Did you mean: 
hughb
Contributor
Contributor

How to tell QLIK not to attempt to associate the tables

I would like to load a set of tables and not have QLIK attempt to associate them at the end of the load.

I don't want to use QUALIFY * as this will end up with all my tables with the tablename in the field

I don't want to have to have a sperate App for each table.

 

 

7 Replies
dplr-rn
Partner - Master III
Partner - Master III

You could rename the common column names.
But overall from a design point of view why bring data in which are not related at all?
hughb
Contributor
Contributor
Author

I want to have 1 App that does the load of all the tables from the database schema and store to QVD files only.

We will do the modelling in another App / QVD file.

Then we can manage the data loads and modelling separately.

dplr-rn
Partner - Master III
Partner - Master III

Thats a typical tiered architecture. thats ok.

but if you want to store the qvds only in this app. just drop the table after you store it

shiveshsingh
Master
Master

Then why don't you create an extractor in Qlikview which extracts the data from the tables and then store it in QVD.

Post this, drop all the tables from the QVW file.

Sufficient?

hughb
Contributor
Contributor
Author

this is what I am doing BUT, after the tables get loaded QLIK sense then tries to do the associations and when this fails, it fails the entire dataload.  At the end of the dataloads I want to say 'Don't try to associate anything'.

 

 

 

dplr-rn
Partner - Master III
Partner - Master III

Why do you need the table in memory post saving into QVD? Just drop the tables
shiveshsingh
Master
Master

Okay, but that is the property of Qlik. If you have same column names, then association will be made automatically.

And you don't want to change the column names and use Qualify operator?