QlikView Revision control / version control / source control software

[#1]

Hi all,

I'm working with a solution where we use SQL server and SSIS as our data warehouse and ETL tool. The data warehouse generates most of the data for our QlikView reports.

Regarding our SSIS packeges we use the Tortoisesvn (http://tortoisesvn.tigris.org/) software for Revision control / version control / source control software, etc.

------

I'm wondering if anyone knows about software we can use for Revision control / version control / source control software for our ClikView soulution?

And tips and advices for stuff we have to think about when implenting such a solution...?

Our current sollution is not good enough where we store al qvw/qvd files on one server and with noe check-in control or "rules" for deployment and change handeling...

Hope any one can help - all advice is appreciated especially experiences anyone might have considering this issue...

[StefanBackstrand]

giakoum; No, that is the responsibility of the source control system.

[#3]

I struggle a little after recreating my document. Variables are all empty. Should I set them in my script?

[StefanBackstrand]

Yes. Data is not contained in the definitions.

[jp_golay]

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

[maksim_senin]

Hi EBI Experts,

Could you please update us on the following points:

1. Whether Version Manager stores a qvw-file (a) at whole with data (can be huge) or (b) just its textual parts (load script, xml schemes of charts, doc params, etc.) without data?

2. If the answer to the 1st question is (b), whether Version Manager stores variable defined via Version Overview dialog (Ctrl+Alt+V) in QV Developer? (the variables which are not defined in the load script)

Thanking you in advance.

Best regards,

Maxim

[jp_golay]

1. The whole qvw is stored in VM but we have a default option to clean the data content so we can store only the app structure.

2. Yes we store all the variables (script ones and GUI ones). They are also present for versions compare and we have an option to store distincts values in VM for each target server publication

   For example variable ENV = "DEV" in dev server and = "PRD" for production server. It's very useful to define different connections values before publication

[maksim_senin]

Sounds good! But in case we put qvw under version control we loose an ability to merge/cut changes at the level of source code... anyway, thank you, will keep in mind.

[jp_golay]

We plan to add the -prj xml files to vm in a future release and to add the diff / merge features to Version Manager comparing all xml files in one shot. Also we will keep all the variables values to VM and reinject them to the generated qvw from the -prj files after reconciliation/merge

We also wait for the opening of QV Source Control tools to others to develop an addin to QlikView

Regards, Jean-Philippe Golay CTO of ebiexperts

[#10]

Hi Stefan.

Create a new document and save it with the same name, but opening is still blank.

Can you tell me what my error please?

[#11]

Hi Jean,

Is the new release of VM is available now with the above mentioned features?

Regards,

Anosh Nathaniel