Skip to main content

Enabling multi-language natural language questions in Qlik Sense Enterprise on Windows

By default, Insight Advisor (in-app) in Qlik Sense Enterprise on Windows only supports English. To enable other languages, you need to set up a multi-cloud deployment with a Qlik Cloud tenant. For more information on available languages, see Supported languages.

Information noteWhen using Insight Advisor Chat in multi-cloud deployments, multi-language natural language questions are not supported.
  1. Set up a multi-cloud deployment with a local bearer token, see Multi-cloud Setup Console - Deployments.

    Information noteThe API endpoint should have a “/” at the end of URL if not already present . For example, if the Qlik Cloud URL is https://demos.qlik.com, the API endpoint should be https://demos.qlik.com/.
  2. Enter the name of the deployment as the --multi-cloud-deployment-name configuration parameter for the nl-parser in the Service Dispatcher services.conf file.

    Do the following:

    1. Stop the Qlik Sense Service Dispatcher, which handles the execution of the Qlik Licensing Service.

    2. Navigate to the services.conf file, which by default is located in %Program Files%\Qlik\Sense\ServiceDispatcher\services.conf.

    3. Locate the section [nl-parser].

    4. Under nested value [nl-parser.parameters], add a new parameter: --multi-cloud-deployment-name=.

    5. For the value --multi-cloud-deployment-name, add the name of your Qlik Sense SaaS deployment.

    6. Save and close the services.conf file.

    7. Add a system variable named NLU_MULTI_LINGUAL and set its value to true.

    8. Open the capabilities.json file located at C:\Program Files\Qlik\Sense\CapabilityService.

    9. In the capabilities.json file, add a feature flag named NLU_MULTI_LINGUAL and set it to true.

    10. Restart the Qlik Sense Service Dispatcher and the Qlik Sense Proxy Service.

    11. If you have a multi-node installation, repeat these steps for all the nodes in your installation.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!