I'm looking for an facility to create versions from Qvw files and qvs files.
I want to distinguish between script and application. I know, that i can save the application without data and i know, that i can save my script seperatly.
But If i want to load my script into my application, qv create a new tab and insert the complete script into this tab.
What is the best practice to manage more than one Qvw or qvs file.
Another nice way in QV10 is the project-folder! If you want to use a Source Control Management System, that's maybe an option for you! See attached .pdf!
Thank you. But I Still have a problem. In our company we use svn for java Projekts. So I Think, that these file's are easy to compare. But how it works wirh qvw files.
What must i do, that it works?. At the Moment i have 1 qvw file call: Umsatzreporting.qvw.
In this application is one script with 7 TAB's (e.g Dimensionen, Verkäufe, Produkte) The application has 5 Arbeitsblätter(sheets). So what must i do to use svn ?
But my biggest problem is, what will i do with my data. My application has a size of more than 500 MB. Eventually, the disk full
SVN is not good for versioning large binary files (true of most, if not all versioning tools). I use a VBS script that extracts the layout files (which are text and can be versioned efficiently) and commits them to an SVN repository.
The attached ZIP contains a BAT file and a VBS script. The BAT is fired by a scheduler (I used the Windows scheduler for this). The BAT file calls the VBS script to extract the layout files to a work folder. The BAT file then calls SVN to commit the files to the respository. It also saves an SVN diff report to a log file.
You will need to edit the BAT file to match the paths on your system.
Another option is to load the application with the NODATA option and version control that. It is still binary, but much smaller.
Although V10 can separate the layout from the data using project files, I find that this is clunky at best - but your mileage may differ.
Jonathan
Logic will get you from a to b. Imagination will take you everywhere. - A Einstein
QV10: next to your Umsatzreporting.qvw create a folder called "Umsatzreporting-prj". The next time you save the .qvw Qlikview will generate seperate files for script, sheets, objects,etc. ! See also the screenshot on page 7 in the .pdf I attached previously. See also Qlikview Developer Manual Chapter 8.1 "QlikView Project Files".
These files are textfiles and can be checked into your SVN easily! Don't checkin in the complete .qvw - as you said: it's a binary file.
The Project Files win over the definition in the .qvw. If you edit for example the "LoadScript.txt" in a 3rd party editor, next time you doubleclick Umsatzreporting.qvw QlikView will load the updated script from "LoadScript.txt".
I saw that you defined a folder structure for the application:
Development 01_QvdGenerators QVD 02_DataModell 03_Application 98_Resources 99_Scripts Production ...
Could you give me more information about this structure or best practices to structure a big project? I just start a project and I want to use best practices.
Hi Markus! qIn the german QVDeveloper10SR1 manual I see the information in section "7.1 QlikView Projektdateien".
My folder structure comes from the 3-layer model often used to do bigger projects:
Layer 1: QVDGenerator is used to extract data from the database and store transformed tables as .qvds Layer 2: Datamodel - read qvds and create actual datamodel Layer 3: Binary load datamodel for "Qlikview Professionals" to create layout
This approach is frequently used. Maybe it seems to be some overhead for you right now, but as the project grows it's more handy than having everything (Script, data, layout) in one big .qvw!
If you are really going for a small project, then use the INCLUDE statement and simply check in the scriptfile into SVN. This is a good startpoint. And if the project grows you can apply this more advanced 3Layer-approach later on as well..
