Qlikview vs TFS

[#1]

I titled this Qlikview vs TFS because I feel it's a battle between them.

I am using QV 11 and TFS 2010.

We have 2 servers a DEV and a Prod.

Sometimes we do dev on our local machines too.

We tried using DEV with TFS and then just copyng the QVD's to Proudction but ran into some annoyances.

Maybe we are doing something wrong.

How do you use TFS with QLikview?

Issues:

Qlikview is not really a multi developer system so if we have project1 version 1 that we are developing and we put that into TFS and the QA team is testing, we may want to make a copy and work on features as version 1.1 but we can't really do that because we can't copy version 1.1 over the version that is in TFS.

We could add version 1.1 to TFS as a new version but that's not really the way TFS should be used.  1 TFS application should have multiple versions checked into TFS.

I have read the TFS whitepaper but am still confused and would love to hear from those using TFS with QLikview to figure out some best practices.

Thanks

-Dan

[paul_scotchford]

Did you solve your TFS issues ?

Seeing as this is an old post.

We are looking at ways to use our TFS workflow with QV versioning and deployment.

[amars]

Hi Dan,

It is really a pain in Qlikview to have a multideveloper environment. Attached is a qlikview document for versioning tools. As these are third party tools they largely depend on the .prj folder to do the versioning.

Just to add on if you wish to test create your .prj folder and remove your .qvw file and place it somewhere else now create a blank file and name it exactly same as your previously file. keep it in the same folder. Now close and open it you will see all your objects tabs created.

Thanks....

[#4]

I totally agree with the members on issues with Qlikview and TFS. The complication that I see with TFS and Qlikview is that it generates different changesets for the different type of changes that we would do on a project - one for add, one for delete and one for edits.

However, one of the options we are exploring right now to identify the production version versus development versions is to use labels when an application is released to production. Thus when a defect is reported on the production version, we can quickly retrieve it based on the label and have it fixed and then rolled in to the development versions.

I hope this helps but it is obvious that Qlikview and TFS are not yet a match made in heaven.

[Anonymous]

Hi

Have a look at this Blog Post, and if you wish join the Group it mentions.

Introducing the QlikView Deployment Framework

I have not read all the PDFs in it yet, but I think it would be a best place for you ask this question.

I am using QlikView with SubVersion [as opposed to TFS] and yeah it is useful ['ish] but there is certainly scope for improvement in the QlikView vs. Source Control handshake.

Best Regards, Bill

[bob_zagars]

Bill,

This link is dead.

Bob

[swuehl]

Looks like a time inconsistency in (web) space...

http://community.qlik.com/blogs/theqlikviewblog/2013/11/15/introducing-the-qlikview-deployment-frame...