Qlik Community

Ideas

Vote for your favorite Qlik product ideas and add your own suggestions.

Announcements
Customers, Partners & Luminaries only: You're invited to a Data Analytics Roadmap session. Read More

Integrated versioning system

Partner
Partner

Integrated versioning system

Hello,

Well, everything in the title. This idea is about an integrated versioning system. Basically, my raw thoughts:

-in QMC, you would have several options :
       .Always keep previous version (with data) +a max quantity of version you save (empty meaning "all")

       .Always keep previous version (without data) +a max quantity of version you save (empty meaning "all")=> save a lot of place when you have huge applications

       .Ask the user if he want to version or not and with or without data +a max quantity of version you save (empty meaning "all")

when the user publish an app, the publish popup allows him to save a comment. However, he can consult all the versions from hub or qmc and according to his right downgrade to a previous version with the date of publication.


Sorry, it's a little messy.

Best regards,

Simon

Bi Consultant (Dataviz & Dataprep) @ Business & Decision
8 Comments
Partner
Partner

That would be a nice first starting point for a versioning system. But it should be also possible in an comfortable and efficient way to move sheets (and master elements; see also topic shared master elements) between versions. 

Another point is an improved Qlik script editor, debugger and generall code management with versioning in this area. Today we store all our scripts in an external folder structure which can be versioned with GIT, Subversion or other common systems and use $(Include=...) to start the scripts from inside the apps. But the handling of code with includes in the debugger is an nightmare and beside many missing features very slow. 

Therefore in the context of versioning system it would be important to rethink the hole process inclusive handling of external Qlik scripts in includes (with usage of sub/call). Which are currently the only good way to share common reuseable code between apps or sites.

Partner
Partner

I think that out-of-the-box integration of Qlik Sense with an external repository like GitHub or BitBucket is a must. Today many developers use the nice workaround with $(Include=) but this way you lose the script editor debug/suggestions or have to employ a more complex workflow like write code and test it in one app to benefit from Qlik script editor functionality, then transfer to your repository of choice. Qlik guys, any comments on this? I have heard this request from many developers and it has several times been a topic at Qonnections where different groups present their solutions.

Luminary
Luminary

I plan on asking about version control at a forthcoming luminary meeting :-). I agree that for enterprise scale projects it is essential. Plus the use of additional third party tools that work in this space is not always possible or desired by a lot of orgs.

Partner
Partner

Hello

You should give a try to https://gitoqlik.com/ (chrome extension)

This kind of tool/solution sould be a native solution in qlik sense (even if it's working well as an extension !)

 

Luminary
Luminary

We need to separate the developer experience from the end-user ("business analyst") experience - both need versioning imho. As a developer I am happy using Git and server repos like Bitbucket or Github, whereas a BA will want object, sheet, app drag and drop versioning capability.

Chrome plug-ins have limitations - they are not always allowed and of course are browser specific.

I can confirm that versioning was discussed on the recent call ( but sadly NDA can't say more at this stage).

Partner
Partner

@mcilwricka thanks for your feedback. Maybe you can help get someone from Qlik in here once you have a call with them. They can either acknowledge this is on their roadmap or being worked on, collecting feedback, etc. It's a bit unfortunate when we don't see much traction from Qlik in this forum.

Luminary
Luminary

@Ian_Crosland are you able to provide any sort of info here ? Thanks.

Employee
Employee

Hi

Thanks for submitting, its something which is on the Qlik roadmap and looking to cover use cases which would satisfy the ability for multiple Qlik application builders to be able to collaborate on both a script level and object level within the sheets.

Status changed to: Open - On Roadmap