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

Announcements
Congratulations to the new Qlik Luminary and Partner Ambassador class! Meet them here
cancel
Showing results for 
Search instead for 
Did you mean: 
Shivam22
Contributor III
Contributor III

QVD is not loading with new fields

Hello All,

 

On Qlik Cloud, I have an existing QVD storing a dataset. I'm trying to add new fields to the code and store them in the same QVD, it loads successfully but it doesn't seem to load the new fields. What might be the reason?

 

Thank You!

Labels (2)
7 Replies
rwunderlich
MVP
MVP

Can you post your script? One possibility may be that you are loading the old QVD followed by the one with new fields and you failed to used the Concatenate keyword.

-Rob

Shivam22
Contributor III
Contributor III
Author

Hi ,

 

Thank you for reply,

it's simple and direct code, i have no idea why it is not adding new fields to existing QVD, but new fields show up when i change QVD name.

Test:
load * ;
SQL
from table ;

store test into [lib://Test Aanlytics:DataFiles/test.qvd] (qvd);

 

Thanks alot

Vegar
MVP
MVP

Is the script below the only thing that happens in your script?

Test:
load * ;
SQL
from table ;

store test into [lib://Test Aanlytics:DataFiles/test.qvd] (qvd);

Please make sure that you don't have a `store table into [lib://Test Aanlytics:DataFiles/test.qvd] further down in your script that overwrites your qvd. What happens if you add an exit script right after the store command? 

rafaelencinas
Partner - Creator II
Partner - Creator II

I have some ideas about

 

1 - You are trying to add some data into QVD already existent ( like incremental load )

In this case you must load your first QVD and concatenate your New Data

MyQVD:

Load * from ActualQVd ;

Concatenate(MyQVD)

Load * from YourDataBase

 

2 - You have a Table in Memory with the same structure

When you load a table with the same strucuture (number of fields and names) , Qlik auto concatenate data, and your new data join the table in memory, not load

Try:

YourTable:
NoConcatenate
Load * From YourDatabase;
(Cloud) 
Store YourTable into [lib://YourLib:DataFiles/YourQVd.qvd](qvd)
(Windows) 
Store YourTable into [lib://YourLib/YourQVd.qvd](qvd);

 

3 - You are storing in another place

In QlikCloud, there are spaces, and in this case you need to check if you are storing in the same Space

Lib://DataFiles/YourQvd.qvd(qvd) is your Personal Space

Lib://YourSpace:DataFiles/YourQvd.qvd(qvd) is the space YourSpace

 

Bye!

 

"Without data, you're just another person with an opinion." — W. Edwards Deming.
PrashantSangle
MVP
MVP

Instead of using Select * ... try with Select <enter all field required for reporting> 

then before storing the qvd validate data in same extractor only that you are able to pull all fields..

 

Regards,

Prashant Sangle

Great dreamer's dreams never fulfilled, they are always transcended.
Please appreciate our Qlik community members by giving Kudos for sharing their time for your query. If your query is answered, please mark the topic as resolved 🙂
Amit_Prajapati
Creator II
Creator II

Hi @Shivam22 ,

If you're working on a SaaS platform and something goes wrong, you can search for the relevant QVD file and click on Compute in the details section. This action refreshes the QVD metadata—updating fields, row count, and data size.

Amit_Prajapati_0-1760332209429.png

nevopotokcloudinary
Creator
Creator

We ran into this exact behaviour too in SaaS — we added new fields to a script, the QVD reload succeeds, but the new fields don’t appear when we load it again from the same QVD.

Workarounds we found:
• After the QVD store step, in the cloud UI find the QVD file and click “Compute” / refresh metadata. That forced Qlik to recognise the new columns. Qlik Community
• Make sure you’re storing into exactly the same QVD path (same space & lib://) – if you end up storing a similarly-named file in a different space, the load may silently pick up the old version. Qlik Community
• If the QVD previously had fewer fields, loading it with LOAD * FROM [that.qvd] may still only pick up the original structure if the system didn’t refresh metadata. Consider explicitly listing the fields (including new ones) or re-creating the QVD. Qlik Community+1