Skip to main content
Announcements
Join us at Qlik Connect for 3 magical days of learning, networking,and inspiration! REGISTER TODAY and save!
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Merging two documents

Hi Community,

I have a ProjA.qvw in which the source is DB. Using ProjA.qvw as binary load i created ProjB.qvw and ProjC.qvw.

ProjB.qvw has the historic data. ProjC.qvw has current data. Now the historic data is dropped in database and there is no source to get it back.  But the qlikview does has the historic data and its not possible to reload the data again.

So how can achieve this, I need to add the historic data to the current data.

jaganstevedark

7 Replies
Colin-Albert

You can export the historic data to QVD files either in the script (with a binary load first) using the STORE command, or you can export the data from a chart to a QVD in the front-end.

Then once you have the QVDs (and have saved a copy of them to be sure!) you can load and concatenate your live data.

stevedark
Partner Ambassador/MVP
Partner Ambassador/MVP

Can you do a binary load of the historic data and then append new in the

load script?

Alternatively, you could do a busy load and then a store from all the

tables to QVDs. These can then be used more flexibly.

Hope that helps.

Steve

Not applicable
Author

Thank you Colin albert. I Did the same as you told.

For some reason, Its generating duplicate values.

Not applicable
Author

Thank you so much for reply.

jagan
Luminary Alumni
Luminary Alumni

Hi Walter,

Check this link and create QVDs for Current and Historic data from the Qlikview files and then load this and concatenate into a new qlikview file.

Storing all tables in Qlikview file to QVD

Regards,

Jagan.

Colin-Albert

Have you loaded the same data twice? One using a binary load and again from QVDs?

If you have added the historic data to QVDs, then your app just needs to load from the QVDs and not use a binary load.

stevedark
Partner Ambassador/MVP
Partner Ambassador/MVP

You may find if you are merging old and new data, and there is a risk of duplication, that you want to look at WHERE NOT EXISTS.  This is covered in this post on incremental load strategy:

http://www.quickintelligence.co.uk/qlikview-incremental-load/

Steve