Skip to main content
Announcements
See why Qlik is a Leader in the 2024 Gartner® Magic Quadrant™ for Analytics & BI Platforms. Download Now
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Source Control/Version Control/Change Management

Hi all,

I'm curious if there are any recent developments in the source control / version control for Qlikview applications.

The main issue arises when there are more than 1 QV developers working on the same exact load script(UI).

Any suggestions/solutions would be highly appreciated.

Thanks,

Rocky

1 Solution

Accepted Solutions
boorgura
Specialist
Specialist

Hey DV,

thanks for taking me back in time... nostalgic. Big Smile

So - for version control or better change management -

and of course, effective performance (in terms of reload time) - we've opted for a n-tiered model.

We separated out the scripts as qvs files from the QVWs, so even the end data model load - where we integrate all the FACT tables, we will have several script files, which can be worked on in parallel.

The only bottle neck left out would be the UI. which of course, still needs to be worked in serial.

View solution in original post

16 Replies
IAMDV
Luminary Alumni
Luminary Alumni

I understand that the above post is 15 months old. However, I am looking for a similar solution in QlikView.

Rocky / other expers please can you help?

TIA!

Cheers - DV

boorgura
Specialist
Specialist

Hey DV,

thanks for taking me back in time... nostalgic. Big Smile

So - for version control or better change management -

and of course, effective performance (in terms of reload time) - we've opted for a n-tiered model.

We separated out the scripts as qvs files from the QVWs, so even the end data model load - where we integrate all the FACT tables, we will have several script files, which can be worked on in parallel.

The only bottle neck left out would be the UI. which of course, still needs to be worked in serial.

IAMDV
Luminary Alumni
Luminary Alumni

Rocky - Thank you very much for prompt reply. I am fairly new to Qlikview and I guess I need to digest your solution.

IAMDV
Luminary Alumni
Luminary Alumni

Rocky - Please can you tell me on how to seperate the script file from the QVW document? Sorry I should have asked you this question earlier!

boorgura
Specialist
Specialist

In the script editor view -

Edit --> Export to script file --> you can save the script as a .qvs file.

Then have all the scripts to be included in the QVW.
you can use the Edit --> Include option.

(P.S. you will have to clear out the entire script from your QVW)

A qvs is just a text file. (can opened with notepad/wordpad as well)

Not applicable
Author

In QlikView 10, you can also create Project Files (see Book 1, section 8.2 in the QlikView Reference Manual.pdf).

Every sheet, object, etc. in your document is broken out into a separate XML file. No data is included in the files. This is perfect for projects requiring source control.

I'm not sure how to re-constitute a QlikView document from the project files (the manual only describes it as a one-way process). Maybe someone else knows?

IAMDV
Luminary Alumni
Luminary Alumni

Simon - Thanks for the update. We are still using Version 9 SR3 and we are planning to upgrade to Version 10 very soon. I hope that solves this issue.

Thanks again for taking time to help.

Cheers - DV

vidyut
Partner - Creator II
Partner - Creator II

Devil It is a two way process. Delete the QVW File. Create a new QVW File with the same name. Save it., Close QlikView and open it again, and you will find the old app imported in there. The data will be missing anyway.

Check, this should work.

IAMDV
Luminary Alumni
Luminary Alumni

Thank you Vidyut.