Best practise for having multiple developers on a single QlikView app

[#1]

hi guys,

at the moment we use a source control system called Serena Dimensions to store our source files.

We have a couple of developers who both work on the same dashboard so have to check the work out, make a change, check it back in for the other person etc.

Is there a 'better' way of doing this that any of you are aware of?

Regards,

Matt

[Oleg_Troyansky]

Not really, unless you can split the work between them into two QVW documents - for example, if one is only developing script and the other one is developing UI, you could split the document into 2 and use binary load to load the results of the script into the UI. Otherwise - no better way...

[#3]

Here are a few things you can try:

Move all expessions to qvs or csv files.

Move all of the loading scripts to qvs and do not embed them in the qvw file

In 9.0 and later, you can export and import sheets. If the developers are working on separate sheets, the first person can check in the changes then the second person can export his/her own sheet and import the sheet into the checked in version.

If both people are working on the same sheets then they need to coordinate well. Usually this means the one with most changes check in first and the person with fewer changes reapplies the changes.

Alternatively, you can exporting the entire document in xml format and attempt to merge the two. The xml file format not documented (as far as I know) and can be very large so correctly merging two xml files can be difficult. In my experience, better coordination saves more time compared to merging.

[#4]

Hi matpj,

You can use SVN. Multiple developers can work locally and then commit the application,which updates the application residing on the SVN server.So the application on the SVN server is always the latest and you can also get the latest updated application from the server.

Hope this helps.

Regards,

Snehal Nabar