Qlik Sense integration with Version Control Systems

[vadimtsushko]

What kind of workflow for integration with VCS is available now or will be available in Qlik Sense Server environment?

• Full application export into text/xml format (analogue of -prj forders for QlikView)
• $(include...) $(must_include...) directives for load scripts
• Maybe export/import of Master items into some sort of text files? 

Best regards, Vadim

[Miguel_Angel_Baeyens · Accepted solution]

Hi Vadim,

Many thanks for your interest, but we should wait until the Qlik Sense server offering is publicly available!

However, here are a couple of things that can help:

• Qlik Sense works with LIB statements, that you refer by name. In my case, I have just created a new connection to C:\DocFiles\ named as "Root", so I load from "FROM 'lib://Root/Test.xls'"
• $(Include=) variables will work in the script if you are already using them

Sharing QVF files with Qlik Sense Desktop requires to be in the same folder as they are in the computer where they were generated.

Miguel

[vadimtsushko]

Thahk you for answer. Will wait for Qlik Sense Server release then

[chrisbrain]

Would like to re-ask this question now version 1 is out - specifically with regards to whether there is an equivalent of the -prj folder system in QlikView to allow you to separate out the various parts of a QVF file into separate files for source control?

[jochem_zw]

Hi Chris,

I don't think PRJ is possible with Qlik Sense (not for sure)

All document and object information is now in the Central repository

[chrisbrain]

OK thanks - would be interested to know any techniques available for adding Qlik Sense apps into GitHub.

[Allardata]

Anyone with some new insight on this matter?

Is it possible to integrate Qlik Sense applications in version control?

Any possibility to export the script?

That way I could at least control most of the (business) logic, combined with the binary qvf file is a good starting point.

[vadimtsushko]

You never have to export your script if your script have one line:

    $(must_include=actual_script.qvs);

[andrewpettit]

That might work but does not address the missed functionality offered by the use of the PRJ folders which allowed you to also identify changes in the UI and not just the script.

[vadimtsushko]

Allard specically asked about the way to version script code.

BTW even in QlikView I use version control only to version script code - with that same technique.

Version control systems are the best tools to work with programming code. For dealing with gigantic XMLs presented massive UI application IMHO they mosltly useless.

When I diff two versions of my script file I get very usefull information.

When I diff two version of PRJ directory state - it is a totall mess. Only meaningfull action that I can perform with stored state is to restore that previous version.

But I can do that without VCS - just saving my UI applications (with reduced data) with names with timestamped suffixes