topic Source Control/Version Control/Change Management in QlikView

Source Control/Version Control/Change Management

Wed, 09 Dec 2009 22:38:49 GMT

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

Source Control/Version Control/Change Management

IAMDV — Tue, 29 Mar 2011 09:32:57 GMT

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

Source Control/Version Control/Change Management

boorgura — Tue, 29 Mar 2011 13:35:55 GMT

Hey DV,

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

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.

Source Control/Version Control/Change Management

IAMDV — Tue, 29 Mar 2011 13:57:12 GMT

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

Source Control/Version Control/Change Management

IAMDV — Tue, 29 Mar 2011 13:59:52 GMT

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!

Source Control/Version Control/Change Management

boorgura — Tue, 29 Mar 2011 14:51:20 GMT

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)

Source Control/Version Control/Change Management

Tue, 29 Mar 2011 16:24:31 GMT

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?

Source Control/Version Control/Change Management

IAMDV — Wed, 30 Mar 2011 11:15:30 GMT

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

Source Control/Version Control/Change Management

vidyut — Wed, 30 Mar 2011 11:45:54 GMT

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.

Source Control/Version Control/Change Management

IAMDV — Wed, 30 Mar 2011 12:09:16 GMT

Thank you Vidyut.

Source Control/Version Control/Change Management

Wed, 31 Aug 2011 19:06:02 GMT

Where does the QVW file and -prj folder need to be stored. I tried on my local machine and when I open the QVW or add objects it is not populating the folder with the XML. Is there a setting you need to enable?

Source Control/Version Control/Change Management

Thu, 12 Jan 2012 08:59:46 GMT

The QVW file and -prj file needs to be in same folder. After making any change in QVW just save it, and refresh the -prj folder, the corresponding changes will get incorporated in respective xml files.

Source Control/Version Control/Change Management

Thu, 12 Jan 2012 10:45:36 GMT

The -prj files will get updated once you save the Qlikview application, but there are few steps which need to be followed when this process is reversed like generate Qlikview application (without data) using -prj files:

In this case you will be having -prj files in <QV app>-prj folder and you need to create corresponding Qlikview application.

1. Rename the <QV app>-prj to some other name <QV app>-prj1 so that the newly created blank qvw will not modify -prj files.

2. Create a blank qvw file with name as <QV app>.qvw and save it.

3. Close Qlikview and rename the <QV app>-prj1 to <QV app>-prj

4. Open the newly created blank qvw.

Now your original Qlikview application will get generated without data. To add data just reload the application.

Source Control/Version Control/Change Management

Tue, 14 Feb 2012 17:45:41 GMT

We've been watching for QV 11 SR1 for a bit, any news on the latest? Since it looks like SVN support will be part of this release.

Re: Source Control/Version Control/Change Management

Tue, 14 Feb 2012 17:46:04 GMT

We've been watching for QV 11 SR1 for a bit, any news on the latest? Since it looks like SVN support will be part of this release.

Re: Source Control/Version Control/Change Management

jp_golay — Fri, 01 Jun 2012 08:28:47 GMT

Hi,

We just released Version Manager for QlikView, it's more than a source control tool because it can deploy your applications to the QlikView Servers.

Very simple to configure and use the tool have a long history and experience of by deployments with SAP products.

Ask for a demo at info@ebiexperts.com or http://www.ebiexperts.com

Re: Source Control/Version Control/Change Management

IAMDV — Fri, 01 Jun 2012 09:52:33 GMT

Thank you. I have requested for the web demo.

Cheers,