Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik GA: Multivariate Time Series in Qlik Predict: Get Details
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Hidden/encrypted include files?

Hi,

Suppose you have hidden all your load scripts and you want to use the $(include)-feature for a library-like approach. Is there any way you can hide/encrypt the include files, so that you are not exposing your library-functions.

Best regards

Steen Olesen

4 Replies
Miguel_Angel_Baeyens

Hello Steen,

It seems to be something related to your operating system. The QVS file format is plain text, so it is the input of the $(include=file). You can configure permissions in your system so users cannot read the file.

So depending on your system, I'd rather use the hidden script approach, which is only accessible using a password, and not visible to users.

Hope this helps.

Not applicable
Author

Sure, you can set the user rights for a specific file, but this will not protect "the knowledge" in the include files.

So, this would mean, that you would have to copy/paste the same code into all your loadscripts, making maintenance quite difficult.

/Steen

Not applicable
Author

Hi Steen,

If you want to keep your script outside the QVW file you can export your script which is given in the edit script .You can keep this in a .txt file and if you want to include this you can use the include function given in the edit script.I think no need to copy and paste your script in the Edit script .

You can use this way also your scripting code will be not visible.Only the include statement will be visible in the edit script.

Regards,

Ravi

Miguel_Angel_Baeyens

Hello Steen,

Since I don't think there is any QlikView function to hide or protect script files, copying the script in the different documents is exactly what I mean. On the other hand, if users don't have access to read the qvs file, they won't see the script in any moment, so the contents of the script will not be accesible in the filesystem nor in the application itself.

Regards.