Suggest an Idea

[simonaubert]

We have used for years, beginning with QlikView .qvs files to reuse some script in several applications.

However, I think that the fact that you need an access to a real repository to store these files is not acceptable in our days :

0/All the logic of Sense is based on web. Except that. Why?

1/Server admins become more an more strict on this point. It's really hard to have access to a repository.

2/How to deal with .qvs on Qlik Sense Cloud?


So the basic idea is to have a space where a developer can write/store/update/read/delete those qvs, of course with given rights. It's time to get modern !!

[AlexOmetis]

In QS Enterprise at least, you can access external qvs files stored on the web (github for example) simply using a web file data connection. Is this what you're after? 

[simonaubert]

Hello Alex,

No, what I want is to not having to deal with files at all. Just like you have app, you would have "macro apps"  (that's the alteryx naming for the same functionnality) with code that you can reuse as you want and with an easy access/read mode.

Today, if you want to see what is really inside the qvs, you have to open it as a file with a text editor. I also want to click on the qvs and see it though the qlik sense editor, with the correct syntax color, etc.

[AlexOmetis]

Ah OK, interesting. I'm not familiar with Alteryx so I don't know about macro apps. So it would be a code/template app/function repository hosted in the Qlik Sense platform and there would be a way to browse / view the repository and reference it in other apps? More integrated to the platform than creating a code repository on an internal git/svn/whatever server with a web front end for browsing?

[simonaubert]

Hello @AlexOmetis ,

That's exactly the idea. Based on that we can even think to some additionnal features such as "macro/qvs" documentation or a "macro advisor" that would suggest to the developer some macros related to his script, based on macro usage frequency (a calendar present in every app) or fields.

Best regards,

Simon

[Klaus75]

But if Qlik goes into that direction it must be fully backward compatible in the sense that it muste be possible to structure the "QVS" repository freely with "subfolders / packages", free naming and all the existing scripting artefacts like inlcude, subs/calls and so an otherwise to much existing (framework based) code will break.

But this feature would only usefull if in the same step the editor get much more functionality, the debugger gets improved and a versioning gets integrated.

Also it is a must have feature than to have the ability to export such "repositories" or parts (="modules") of these Qlik "ETLs" as ZIP of QVS folders as well as import from there so that partners can reuse developments across different Qlik Sites / customers etc.. Which is today the usage scenario for the external .QVS folder structures beside versioning. 

[Thomas_Hopp]

Thank you for sharing this idea with us. As part of our Cloud offerings we recently delivered the ability to store artefacts such as QVD's and or other Data Files + Data Connections as well into Spaces. To reuse those you can use a relative path to cross reference those within Apps which are stored in other spaces. This is the start of reusing and cross referencing content. There will be more delivered along the road and I'm adding that particular idea to our backlog to make sure we are using examples like this while we are working on new capabilities.

Here is where you can find more details about the capability I'm talking about above: https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/Spaces/managing-data-res...

Thomas

[Meghann_MacDonald]

From now on, please track this idea from the Ideation portal. 

Link to new idea

Meghann

NOTE: Upon clicking this link 2 tabs may open - please feel free to close the one with a login page. If you only see 1 tab with the login page, please try clicking this link first: Authenticate me! then try the link above again. Ensure pop-up blocker is off.