Qlik Sense is a developing product; hence, certain features are not active when running the Desktop version in its standard mode. A prime example of this is running Windows command-line statements or external programs, such as the 7zip file compressor. Both these activities are not possible if Qlik Sense runs in its standard mode. In order to get these functionalities to run, we need to activate the legacy mode. However, you must be aware that enabling the legacy mode has security implications, if the application is deployed on the Sense server. You do not have control over the data connections in QMC (if the legacy mode is activated). The library security features may also be lost; moreover, the user has access to the entire filesystem on Qlik Sense Server because the account running the Qlik Sense Engine Service has administrative privileges. Activating the legacy mode requires changing a parameter value in the settings.ini
file for Qlik Sense Desktop. In the Qlik Sense Server, you must have an Administration Role to access the QMC.
The recipe is only valid for Qlik Sense Desktop:
- Make sure that Qlik Sense Desktop is closed before opening the
settings.ini
file. - Open the
settings.ini
file that is, by default, stored underC:\Users\{user}\Documents\Qlik\Sense\Settings.ini
, as shown in the following screenshot:
- Change
StandardReload=1
toStandardReload=0
. - Save the file and start Qlik Sense Desktop in order to run it in a legacy mode.
Changing the value for the StandardReload
parameter in the settings.ini
file enables the legacy mode in Qlik Sense. When running in legacy mode, any of the scripts in Qlik View can be directly used in Qlik Sense. This will also allow us to use the library connections.
Qlik Sense has the ability to use the same script that is found in any QlikView file. You can also use a binary load statement in Qlik Sense in order to load the entire data model from an existing QlikView file. We can also run Windows command-line statements.
- The Executing command line programs within the script recipe in Chapter 3, Scripting