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

Announcements
Qlik and ServiceNow Partner to Bring Trusted Enterprise Context into AI-Powered Workflows. Learn More!
cancel
Showing results for 
Search instead for 
Did you mean: 
JohanLind1979
Contributor III
Contributor III

Full table not loaded when connected to data model

I add a table (qvd with 38000 records) to my data model and if I load the table as a stand alone table I get all 38000 records but if I add a key field to connect to the rest of the data model I only get 350 records. Never seen this behaviour before. Why is this happening and what can be done?

Labels (1)
1 Solution

Accepted Solutions
Vegar
MVP
MVP

It would help to see your script thinking order to understand what you are trying to do. As @Or states above,  the other data in the data model should not affect which transactions you load into the data model.

Are you loading the data in question the same way in both scenarios? Or could it be that you are telling qlik to reduce the load by adding using JOIN, KEEP, or EXISTS? Those three keywords are typically used to reduce data loading into a data model.

A second question.  How do you determine that you only get 350 records? Is it by looking at the rows count in the data model viewer, using NoOfRows() in the script, looking at the rows count in a table object in the application,  or other? Using the later, front end, approach can be tricky as Qlik will only display every unique combination of data once even if you have duplicate records.

Final question. Do you use Section access your data model, could it be that adding that other table , activates the Section Access for your user and thereby reduces the records you see?

View solution in original post

3 Replies
Or
MVP
MVP

It'd be helpful if you posted the code in question. Generally speaking, loading a table with or without a key field does not impact the number of rows returned unless you tell it to (e.g. through a JOIN statement, Exist(), or some other means). 

Vegar
MVP
MVP

It would help to see your script thinking order to understand what you are trying to do. As @Or states above,  the other data in the data model should not affect which transactions you load into the data model.

Are you loading the data in question the same way in both scenarios? Or could it be that you are telling qlik to reduce the load by adding using JOIN, KEEP, or EXISTS? Those three keywords are typically used to reduce data loading into a data model.

A second question.  How do you determine that you only get 350 records? Is it by looking at the rows count in the data model viewer, using NoOfRows() in the script, looking at the rows count in a table object in the application,  or other? Using the later, front end, approach can be tricky as Qlik will only display every unique combination of data once even if you have duplicate records.

Final question. Do you use Section access your data model, could it be that adding that other table , activates the Section Access for your user and thereby reduces the records you see?

JohanLind1979
Contributor III
Contributor III
Author

Section Access! Of course! Thank you so much 🙂