This is a demonstration of how to create a new app in Qlik Sense Enterprise SaaS and Qlik Sense Business.

1. First, login to your Qlik Sense SaaS tenant. Logging in will redirect you to the tenant hub, on the     home tab.
2. To create an app, click on the Add New button at the top.
3. Select New Analytics App.
4. Enter a name, select the space, there’s a link below to a video which discussed more about spaces.
   1. A description and tags can also be added to help organize your apps.
5. Click on the app to open.
6. Add data with drag and drop, creating data connections or go into the script editor.
7. Once in the data manager create connections between the data tables .
   1. The insight adviser will provide some recommendations automatically based on the data.
8. Then press the  Load the Data button to load this data into memory.
9. Now you can create some visualizations.
   1. Use the Insight adviser, go to sheet to create them manually or continue in the Data Manager.

Environment

• Qlik Sense Enterprise SaaS

The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.

Related Content

Tutorial - Build an analytics app

Managing spaces in Qlik Sense Enterprise SaaS

Top 5 Things to Know When Using Qlik Sense Enterprise SaaS

When using a signed license key (SLK) in QlikView, it's not possible to assign professional/analyzer access to users if they do not exist in a directory added in the Directory Service Connectors section. It works fine with LEF license.

Environments:

• QlikView Server 12.50 and later

This is a known limitation.

In QlikView 12.50 SR1 and later, there is a workaround available to turn the Directory service check off and become able to assign licenses to users.

Workaround:

In C:\Program Files\QlikView\Management Service\QVManagementService.exe.config, inside the <appSettings> section:

<add key="AcceptManuallyInputedUsersNotInAD" value="true"/>

This article shows you how to locate your Qlik Cloud license number (Subscription ID) as well as your Tenant Hostname, your Tenant ID, and your Recovery Address. 

Only the Tenant Admin can see the Qlik Cloud Subscription ID and Tenant Hostname / ID.

If you are looking to change your Tenant Alias or Display name, see Assigning a hostname Alias to a Qlik Cloud Tenant and changing the Display Name.

1. Log in to your Qlik Cloud Account and hover over your Profile Icon
2. Click About
   
   
   
   
3. This will show your:
   
   
   • Tenant hostname
   • Tenant ID
   • Subscription ID
   • Recovery address
     
     

Environment

Qlik Cloud 

Related

• How to find Qlik Cloud User ID 

When booting or rebooting a server running the QlikView Webserver service, or attempting a manual start or restart, the QlikView Webserver service fails to start.

The following error is returned in the QlikView WebServer service logs:

System.Net.HttpListenerException (0x80004005): The process cannot access the file because it is being used by another process

Resolution

1. Open an elevated command prompt
2. Run command netstat -anob to return a list of all of the listening port connections on the computer, and the owning process ID of each connection
3. Find the entry for port 80 and note the PID associated with it
4. Open Task Manager and select the Details tab so that PID column is displayed
5. Sort the PID column so that they are listed in ascending order
6. Find the PID determined from step 3
7. Open the Windows Services applet and stop the application/process determined to be using port 80. Or configure the application/process to use a different port other than 80.

Cause

Another application or process is running on port 80, preventing the QlikView Webserver service from initializing port 80 during its start up procedures.

Related Content

How to check which program is using a specific port
How to: Change QlikView WebServer Service port (4750)
How To: Change QlikView WebServer http port (AccessPoint)

When accepting the invitation to an alert, the "Internal Server Error" is displayed

Environment

When accepting the invitation to an alert, the "Internal Server Error" is displayed

Environment:

• Qlik Alerting, November 2020

Resolution

Upgrade to Qlik Alerting November 2020 SR1, or higher, where the issue is solved.

When reloading an app using the Google Analytics either in Qlik Sense or Qlik view it's possible that it fails with one of the following errors in the Web Connectors logs:

<ExceptionMessage>Failed on attempt 1 to GET. (The remote server returned an error: (503) Server Unavailable.)</ExceptionMessage>

Or

<ExceptionMessage>Failed on attempt 1 to GET. (The remote server returned an error: (500) Internal Server Error.)</ExceptionMessage>

Environment

• Qlik web connectors any version

Resolution

R&D is currently investigating how to reduce these errors, but since the error might be triggered due to heavy load in Google's endpoint re-scheduling the tasks might help to solve the issue.

Other potential workarounds would be to place a sleep between API requests or optimize/reduce the amount of data requested

Cause

Quoting google's documentation:

A 500 or 503 error might result during heavy load or for larger more complex requests. For larger requests consider requesting data for a shorter time period.

Related Content 

Qlik Web Connectors Log Files  

Google API Error Responses 

After duplicating a Qlik Sense application, the Script Load Editor cannot be opened.

The following message is displayed:

You do not have access to the data model viewer. The reason for this may be related to permissions, that your device is not supported, or that the app is published or read-only

Environment: 

• Qlik Sense April 2020
• Qlik Sense June 2020
• Qlik Sense September 2020
• Qlik Sense November 2020

Resolution

Information provided on this defect is given as is at the time of documenting. For up to date information, please review the most recent Release Notes, or contact support at support.qlik.com with the ID QB-2904 for reference.

Fixed In:

Qlik Sense February 2021 Patch 1
Qlik Sense November 2020 Patch 6
Qlik Sense June 2020 Patch 14
and later versions 

Workaround:

As a workaround, you can either open the duplicated application on the non "Production" type node or add data in the application.

Cause:

This issue is happening when duplicating a published application without data on a "Production" type node. 
This combination, as a result will prevent the user to open the Script Load Editor and instead getting the message: "You do not have access to the data model viewer. The reason for this may be related to permissions, that your device is not supported, or that the app is published or read-only".

When you load data from spreadsheets, some format settings should be avoided; otherwise, the Qlik Sense server may experience performance degradation such as exhausting memory.

Environment

• Qlik Sense on Windows, all versions

Resolution

Remove the following settings. For more details, please refer to Help: 

Loading data from Microsoft Excel spreadsheets

• Aggregates
• Duplicate headers.
• Cross-table data layout. 
• Merged cells.
• Blank cells where the value is implied by the previous value above. 
• Freeze pane
• Split sheet

Related Content

Loading data from Microsoft Excel spreadsheets

Excel specifications and limits

When you integrate a Qlik Sense object into an application like SharePoint, you need to have consistent connections; whether you use an HTTP or HTTPS on both sides of Qlik Sense and SharePoint. 

Environment

• Qlik Sense Enterprise on Windows , all versions

If you use an HTTPS connection, a third-party SSL certificate needs to be configured.

If you prefer an HTTP connection, tick the box of Allow HTTP in QMC> Proxies.

 Related Content

Changing a proxy certificate

Single integration

When using an external program to run a task as described here, the execution might fail but the status of the external task in the QMC might not get updated accordingly.

In order to handle the failed execution, it's needed to send a request that updates the status in the QMC.

Here is an example of how to update the status in the QMC:

Optional step

If you want to change a specific execution you can use the following code to retrieve the ID needed to change the task status

$hdrs = @{}
$hdrs.Add("X-Qlik-xrfkey","12345678qwertyui")
$hdrs.Add("X-Qlik-User","UserDirectory=DOMAIN;UserId=Administrator")
$cert = Get-ChildItem -Path "Cert:\CurrentUser\My" | Where {$_.Subject -like '*QlikClient*'}
 
$url = "https://qlikserver1.domain.local:4242/qrs/executionresult?xrfkey=12345678qwertyui"
Invoke-RestMethod -Uri $url -Method get -Headers $hdrs -Certificate $cert # | ConvertTo-Json 

Expected response:

id                 : 1fc45154-954b-497f-8752-86aca2180ec4
executingNodeName  : 
status             : 0
startTime          : 1753-01-01T00:00:00.000Z
stopTime           : 1753-01-01T00:00:00.000Z
duration           : 0
fileReferenceID    : 00000000-0000-0000-0000-000000000000
scriptLogAvailable : False
details            : {}
scriptLogLocation  : 
scriptLogSize      : -1
privileges         : 

With the id retrieved we can go ahead and change the result:

$body = '{
  "status":"11",
  "modifiedDate":"2021-03-25T17:00:36.157Z"
}'
$hdrs = @{}
$hdrs.Add("X-Qlik-xrfkey","12345678qwertyui")
$hdrs.Add("X-Qlik-User","UserDirectory=DOMAIN;UserId=Administrator")
$cert = Get-ChildItem -Path "Cert:\CurrentUser\My" | Where {$_.Subject -like '*QlikClient*'}

$url = "https://qlikserver1.domain.local:4242/qrs/executionresult/1fc45154-954b-497f-8752-86aca2180ec4?xrfkey=12345678qwertyui"
Invoke-RestMethod -Uri $url -Method Put -Headers $hdrs -Certificate $cert -Body $body -ContentType 'application/json'

"0: NeverStarted",
"1: Triggered",
"2: Started",
"3: Queued",
"4: AbortInitiated",
"5: Aborting",
"6: Aborted",
"7: FinishedSuccess",
"8: FinishedFail",
"9: Skipped",
"10: Retry",
"11: Error",
"12: Reset"

Environment

• Qlik Sense Enterprise on Windows 
• Powershell

Related Content 

Connecting with Microsoft Powershell
Qlik Sense - Create an external program running a Powershell Script  

Google Analytics has started to show the following error in the web connector logs " Failed on attempt 1 to GET. (The operation has timed out)" and "internal server error" in the script logs when the task is scheduled.

It's very likely that this error it's due to a change in Google's API.

The issue has been fixed and it will be released in QWC December 2020 patch 1. (Expected release mid-February)

The patch will add a new parameter in the deploy.config file that will allow the user to modify the timeouts.

The parameter will be the following one:

  <DefaultRequestTimeoutMs>180000</DefaultRequestTimeoutMs> 

Notes:

• default: 180000 (3mins)
• min: 180000 (3mins)
• max: 5400000 (90mins)

Qlik Web Connectors 

Some customers reported the following error with the Qlik MongoDB connector (within the ODBC connector package) after upgrade to Qlik Sense version November 2020: 

Error: Connector reply error: Unable to connect to database:
20201216T110846.906+0100 Error message:
20201216T110846.906+0100 Please check the values for Username‚ Password‚ Host and other properties.

The issue could be seen and also could be reproduced when you use a non admin MongoDB user in order to reload the data from the MongoDB database (version 3.6).

For more information please check the screenshot:

 When you replaced the user for the MongoDB connection with an admin user the reload was working again:

Environment

• Qlik Sense Enterprise on Windows  November 2020

Cause 

As a result of the investigation:

1) On the reproduction environment we had two users with the same name (here for example "tester") specified in two DB: "admin" and "test_db1" (they had different passwords).

2) Driver from June 2020 release(v. 2.3.7) tried check credentials first for a "tester" from admin DB (as a default) and next from "test_db1" and as credentials fit ok connect by this  user.

3) After fix: Driver from November 2020 release(v. 2.3.12) tried check credentials for "tester" from admin DB (as a default) then connection failed due to credentials does not fit for "tester" from "admin" db.

Resolution

 To specify a user from which particular DB we are trying to use we need to use the additional parameter "AuthSource", like on screenshot:

The variable SET ThousandSep=' ', in  QV 12.50 and above versions has a space ' ' instead of the dot '.' , that is set in the Region Format system settings when the machine language is set to German (Austria). OS Region settings are set to Deutsch (Österreich).

In Windows/Control Panel/Region, the Digit grouping symbol is set to a dot "."

When a new QVW is created in previous QlikView versions (such as 11.20), the system SET variable is correctly configured to SET ThousandSep='.';

When a new QVW is created in QlikView 12.50 versions and above, the system SET variable appears as SET ThousandSep=' '; which doesn't match the Region OS settings.

Environment

QlikView 12.50 and above

Resolution

Works as Designed.

Cause

This is an intentional change that was made when we started supporting more platforms. We do support different regional settings but not "additional settings" (Windows Control Panel\Clock and Region -> Change Date Time or Number formats -> Additional Settings).

Workaround

The workaround consists of changing the load script manually.

Issue description:

Customers reported  an issue with the Monitor in Hub functionality on charts when using their alias tenant. The was that the chart was stuck in the QSB hub in the "generating object" status without showing the chart in the hub at all, even if the customers reloaded the browser. When the customers used the "normal" tenant, they were able to see the chart successfully generated in the Qlik Sense Business  hub.

Environment

• Qlik Sense Business

Resolution

The issue was caused by a software defect which has been resolved and released on the 6th of January 2021.

Workaround:

-

Fix Version:

-

Cause

Product Defect ID: QB-2861

The linked tutorial demonstrates bulk deletion of groups from Qlik Cloud, to support you in scenarios such as where your Identity Provider has sent:

• GUIDs rather than friendly group names
• All groups, rather than groups related to Qlik Cloud
• Groups that you need to remove prior to configuring a different Identity Provider

Access the tutorial on Qlik.dev: Deleting groups in bulk with qlik-cli

If you're a Qlik Enterprise SaaS early adopter, you managed to configure Azure Active Directory as the identity provider for your tenant using the ADFS option in the settings menu. While this enabled users to authenticate from Azure AD, it didn't solve a key problem with this workaround; native Azure group name resolution.

The new Azure AD identity provider settings in QCS include proper group name resolution. But you might be hesitant to switch the configuration from ADFS because you're worried about the impact on existing access control set up in your tenant. Will Space permissions work after the switch? Will users retain all their personal content? Will the switch create duplicate users? This blog resolves these concerns by showing you how to make the switch from ADFS to Azure AD smoothly.

Good news: The app registration in Azure AD remains valid

There's no need to reinvent the wheel and create a new app registration in Azure to support the switch. However, there is a significant tweak to make if you want to take advantage of Qlik's capabilities to resolve group names from Azure. Here are the steps to prepare the existing app registration for reuse in QCS.

Create a new client secret

In all likelihood, you misplaced - or should have lost - the client secret you created when you set up the app registration the first time. It's easy enough to generate a new secret for the app in the certificates and secrets section of the config. Create a new client secret and make a copy of it for use when you update QCS.

Remove groups optional claim from Token configuration

Say what now? Remove the groups claim? Yes, that's right, you don't need the groups claim anymore to obtain a user's groups because the Azure AD setting in QCS contacts the Microsoft Graph API to collect this information, resolving the group names for Azure AD native groups and groups synchronized through AD-Connect.

Add GroupMember.Read.All API permissions

The reason the optional groups claim is not needed is there is an API permission allowing sharing the groups the user is a member of. When the permission GroupMember.Read.All is added to the app registration, Qlik makes a request to the MS Graph on behalf of the user to obtain the group names for which they are a member.

Before you continue! Make sure to grant admin consent for the new GroupMember.Read.All permission. If you miss this step, expect http 401 errors because of the request to Microsoft Graph.

Create a new interactive identity provider configuration in QCS

While Qlik Enterprise SaaS allows for only one active interactive identity provider in a tenant, you can set up more to make it easier to switch from one to another.

For converting from an ADFS configuration to an Azure AD setup it's straightforward but there are a couple of tweaks you want to pay attention to ensuring a smooth transition. Here are the steps:

Copy IdP settings from the existing ADFS configuration

Take some screenshots of the ADFS set up, and record the discovery URL and Client ID to notepad so you can reuse them in the new configuration.

Create the Azure AD configuration

Create a new interactive identity provider selecting Azure AD from the provider list.

Add the discovery URL for the app registration and input the Client ID and the new client secret created earlier in the corresponding text boxes.

Fill out the claims mapping values from your ADFS settings screenshot.

Lastly, to make sure the mapping works properly expand Advanced options and slide the email verified override switch to on.

Create the configuration and save it.

After you authenticate to the new identity provider, the validation screen appears. With the new email verified claim switch turned on, the email shows up signifying the mapping process succeeded. Click through and activate the IdP.

Log out completely. This may require you to log out twice, once as the new validated user, and once as the user you logged in as to create the new configuration.

Log in through Azure and go to a space to add members and view friendly group names.