topic Re: Save as (qvf) via data load script in App Development

Save as (qvf) via data load script

Anonymous — Thu, 23 Nov 2017 08:46:54 GMT

Hi,

Is there any option to save an app as another qvf file using the data load script?

The purpose is to:

- run load script

- in the load script create a loop

- in each step of the loop:

-->filter the data using WHERE clause i.e. Sector = 'first_sector'

-->save as app_first_sector.qvf

- go to next loop iteration

Re: Save as (qvf) via data load script

tomasz_tru — Thu, 23 Nov 2017 09:16:53 GMT

what's the purpose? maybe all you need is on demand app generation (On-demand apps ‒ Qlik Sense)?

if not - it's not possible to save QVF in script loop - only to CSV or QVD - here's my shortcut for doing that the way you need: Subroutines in load script

Re: Save as (qvf) via data load script

Anonymous — Thu, 23 Nov 2017 09:17:49 GMT

You could in each loop save to the data to different qvd files and then create multiple qvf's that load from the appropriate qvd files.

But the best forwards depends on your required end game. If your needs are actually security, as in for some people to only have access to some data and other people to other data then maybe look at this blog post A Primer on Section Access by HIC. It is a few years old, but Section Access security is still pretty much the same in the latest Qlik Sense and a search on Section Access will produce loads of hits.

Re: Save as (qvf) via data load script

Anonymous — Thu, 23 Nov 2017 10:46:13 GMT

The purpose is to create 10 copies of the same app. Every single app should have data filtered by 'Sector' (there are 10 sectors)

Re: Save as (qvf) via data load script

Anonymous — Thu, 23 Nov 2017 11:16:47 GMT

May I ask what the required end game is ?

Is this for data security reasons, as in you only want certain people to be able to see certain data ?

Or is there another reason ?

The reason I ask is that the best way forwards depends on the required end game.

Re: Save as (qvf) via data load script

tomasz_tru — Thu, 23 Nov 2017 11:21:20 GMT

Section Access is not possible? Is it Desktop or server version?

Re: Save as (qvf) via data load script

Ricardo_Gerhard — Thu, 23 Nov 2017 11:25:59 GMT

Dear Grzegorz,

I guess that you want to create a loop and reduce as we have on Qlikview Publisher, creating multiple dashboards, correct?

This resource is available on Qlikview Publisher and will be moved on to Qlik Nprinting (I believe) that is compatible with Qlik Sense.

Regards.

Re: Save as (qvf) via data load script

mdmukramali — Thu, 23 Nov 2017 11:30:10 GMT

Hi,

why don't you try Section Access?

Instead of Creating and Maintaining 10 Copies of the same application which is not good idea,

like if you want to modify an expression in the chart then you have to modify 10 places same expression.

Thanks,

Mukram

Re: Save as (qvf) via data load script

Anonymous — Thu, 23 Nov 2017 11:46:46 GMT

This sector split is for security reasons - allow users to see only their sector.

My recipients will use QS Desktop to open the qvf file.

Is the 'section access' working on QS Desktop too?

Re: Save as (qvf) via data load script

Ricardo_Gerhard — Thu, 23 Nov 2017 11:51:14 GMT

Qlik Sense Desktop is for single user only.

Take a look on this article Section access in Qlik Sense

My suggestion is to use variables in order to controle informations or Qlik Sense server.

Re: Save as (qvf) via data load script

mdmukramali — Thu, 23 Nov 2017 11:52:32 GMT

Hi,

Unfortunately Section Access will not work with QS Desktop.

Re: Save as (qvf) via data load script

Anonymous — Thu, 23 Nov 2017 11:59:35 GMT

OK. Thanks for confirmation.

Normally will I use section access. Unfortunately, this time users have no access to the server.

Re: Save as (qvf) via data load script

Anonymous — Thu, 23 Nov 2017 12:13:46 GMT

Without Qlik Sense Server it will be a bit painful. If Qlik gave everything away for free in the freebie Desktop version they would go bankrupt and there would be no Qlik.

Create a single QVD generator to produce a single QVD with all your data
Create 10 qvf's that hardcod in the load script to only load data required
Distribute the qvf's to people as required

If you goes well and people like Qlik then maybe suggest to those in charge of your money that maybe should consider buying the full server version. As you will in effect have just done a successful Proof Of Concept.

Re: Save as (qvf) via data load script

tomasz_tru — Thu, 23 Nov 2017 12:17:30 GMT

1. Run app that is creating separate QVD's.

2. Use API to reload all the separate end-user apps (each one using different QVD file).

3. Distribute the files.

But this is not the way to do it. It is the moment you should talk to Qlik - if server is not an option, maybe Cloud soultion?

Re: Save as (qvf) via data load script

Anonymous — Thu, 23 Nov 2017 12:26:26 GMT

I agree with you in 100%.

It is 'a bit painful'

We have the server version. The problem is we have not enough licenses...

Re: Save as (qvf) via data load script

Anonymous — Thu, 23 Nov 2017 12:29:44 GMT

This basically doesn't change a lot, because we still have to duplicate apps in case of any amendments in the "main app"

As I said - we have server version, we don't have so many licences to make all people happy

Re: Save as (qvf) via data load script

tomasz_tru — Sun, 10 Dec 2017 06:26:06 GMT

Have you succeeded? What solution have you chosen?

Re: Save as (qvf) via data load script

petter — Sun, 10 Dec 2017 18:01:38 GMT

NOTE! I have made this app to show that the concept is technically possible. This is not meant as any kind of encouragement to break any license rules that is for the Qlik products. It is your own responsibility to check whether your use of this code comply with the licensing of the Qlik products.

Actually by having a MYAPP.qvf with all the data you can create a template for sectors with a single MYAPP.sector X.qvf.

MY_APP.qvf

"MY_APP.Sector='Sector A'.qvf" (notice that you have to separate the APP name from the filter by a period).

Then you can make a pure copy of the "MY_APP.Sector A.qvf" into "MY_APP.Sector B.qvf" and so forth. Then you can do a reload of each and each of them will only have data for the relevant sector.

The load script for "MY_APP.Sector A.qvf" does is dynamic and will use the text between the two periods in the file name as a filter for the field named Sector.

MY_APP.qvf will just have the entire load script for all data and no UI. The entire UI you can create in the "MY_APP.Sector A.qvf" this app will also have this load script:

BINARY [LIB://Apps/MY_MASTER.qvf];

LET WHERE = SubField(DocumentName(),'.',2);

[DATA]:
NOCONCATENATE LOAD
*
RESIDENT
[DATA]
WHERE
$(WHERE);

DROP TABLE
   [DATA];

RENAME TABLE [DATA-1] TO [DATA];
WHERE=;

You might have to do reloads manually unless you use the API. But 11 reloads is not too bad 😉

I have attached the two applications so you can try it out yourself and extend it. You will have to fix the LIB connection in the "MY_APP.Sector='Sector A'.qvf" to the appropriate folder as the one in the app points to my personal folder...

Replace the text (filter-comes-here) with for instance:

Sector='Sector A' will have a data subset where only Sector A data is part of the qvf

1=1 will have a full data set - useful as the development UI template application