This group hosts information related to the Qlik Deployment Framework (QDF). Providing best practices, libraries and utilities that facilitate the recommended setup and management of QlikView or Qlik Sense environments. An understanding of the Qlik platform is recommended before joining this group. Download QDF and documentation here: https://github.com/QlikDeploymentFramework/Qlik-Deployment-Framework/releases
Revision control, also known as version control, source control or software configuration Management (SCM), is the management of changes to documents, programs, and other Information stored as computer files. It is most commonly used in software development where a team of people may change the same files.
As the development team of a QlikView Application grows so does the need for SCM. This document describes some possible approaches to integrating SCM with QlikView using Microsoft Team Foundation Server and the popular Open Source version control system SVN. It further describes typical developer / multi-developer scenarios and how one can take advantage of SCM in these situations.
Hi, it would be nice to see an example on a fully integrated solution with Publisher and server.
We are trying to not add the qvw file to our repository and recreate the app from the prj files.
We are trialing a source control solution using TFS Power Tools. It allows you to map a local drive to the team Project in TFS and then you can check files out and in through the file system.
This means that we can version control the entire container structure in the QlikView Deployment Framework.
I do recommend that you Reduce Data -> Remove All Values from your qvw files before checking in.
I think you need Visual Studio Team Edition for this to work. The Power Tools are a free add-on.
Jerry, we are not using Publisher, but I don't think this would make any difference to the solution. A "deploy" would simply involve copying the entire container subject to your Source Documents folder(s) on the the Publisher server.
Please be very careful with Reduce Data -> Remove All Values:
If you have List Boxes that require one and only one value - this setting will be lost!
Yes, I have noticed that. Is there any programmatic way of enabling this setting?
At least variables are not lost with reduce data like they are with -prj files.
We have Publisher and would like to have a job that gets latest from the repository, reloads and publishes.
At the moment it is not possible without adding the qvw file to the repository.
Or is it?
Always one selected and lost triggers we can handle, but there are other problems.