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

Announcements
Qlik Open Lakehouse is Now Generally Available! Discover the key highlights and partner resources here.
cancel
Showing results for 
Search instead for 
Did you mean: 
draghici1109
Creator
Creator

Loading and Storing a qvd File results in different number of records

Hello, 

I just have a pretty simple code:

COSP:
NoConcatenate
LOAD 
OBJNR, //01
    GJAHR, //05
    KSTAR, //06
   WRTTP AS Realisierungsgrad,
    VERSN, //08
    VRGNG, //09
    BEKNZ, //10
    PERBL, //11
    WTG001,
    WTG002,
    WTG003,
    WTG004,
    WTG005,
    WTG006,
    WTG007,
    WTG008,
    WTG009,
    WTG010,
    WTG011,
    WTG012,
    WTG013,
    WTG014,
    WTG015,
    WTG016,
    WRTTP 
FROM [..\DATA\$(vPraefixDateiName)-COSP.qvd] (qvd);
 
STORE COSP into [..\DATA\PROFIS\$(vPraefixDateiName)-COSP_AusQlik.qvd] (qvd);
 
And yet, the input qvd-File, which contain more Fields as the stored one, namely 733255 records, as I store it into the  COSP_AusQlik.qvd file it does contain only 639661 records. By any means, including extensive tests sugested by ChatGPT :-), I cannot solve this problem. The  COSP_AusQlik should have the same amount of records as the input qvd file.  
 
Any ideas/workarounds?
 
Thank you in advance,
 
Alexandru 
Alexandru Draghici
BICC at Komm.ONE
Labels (1)
1 Solution

Accepted Solutions
draghici1109
Creator
Creator
Author

Dear Marcus,

Dear Rob, 

Dear Aditya,

thank your for your implication and support! This attitude is something that I highly value on our Qlik Forums. 

 

Yet... it is embarrassing for me, and I sense a little bit of shame 😞 … as I found out, that the input file which I used was a false one. I chose the file COSP.qvd from the false directory. I am sorry!

Yet I want to conclude positively: I learned from your responses some important hints how to manage similar problems that might occur in the future.

 

Kind Regards, Alexandru 

 

Alexandru Draghici
BICC at Komm.ONE

View solution in original post

6 Replies
marcus_sommer

Maybe all field-values from your field-extract are NULL and therefore skipped from the load. I could imagine that an added recno() and rowno() in this load and/or here and in a full-load of the source may trace which records are there and which one are missing.

rwunderlich
Partner Ambassador/MVP
Partner Ambassador/MVP

"the input qvd-File, which contain more Fields as the stored one, namely 733255 records, as I store it into the  COSP_AusQlik.qvd file it does contain only 639661 "

Where do you get these numbers from?

-Rob

draghici1109
Creator
Creator
Author

Hello Rob, 

the different numbers of rows in the input and output qvd I get it from the EasyQlik QViewer Tool.

Kind Regards, Alexandru

Alexandru Draghici
BICC at Komm.ONE
Aditya_Chitale
Specialist
Specialist

@draghici1109 ,

If you are adding the rows as dimensions and then checking the count, the duplicated rows might show as a single entry thus reducing the count of rows. Try adding recno() as an additional field in your data before storing the qvd and then check if the count shows correctly.

Regards,

Aditya

marcus_sommer

I use QViewer or Q-Eye usually only for quick looks on the data-structures and meta-data and not for more detailed evaluations but I never noticed any strange behaviour. Therefore I think the shown number of records are correct.

Like above hinted would a quick load within a qvw and the extra record-counters showing the truth - how many records are there as well as which one are missing. If so I would look for NULL's ...

draghici1109
Creator
Creator
Author

Dear Marcus,

Dear Rob, 

Dear Aditya,

thank your for your implication and support! This attitude is something that I highly value on our Qlik Forums. 

 

Yet... it is embarrassing for me, and I sense a little bit of shame 😞 … as I found out, that the input file which I used was a false one. I chose the file COSP.qvd from the false directory. I am sorry!

Yet I want to conclude positively: I learned from your responses some important hints how to manage similar problems that might occur in the future.

 

Kind Regards, Alexandru 

 

Alexandru Draghici
BICC at Komm.ONE