When sending emails using the Mail Connector in Qlik Application Automation, special characters in the Subject field may not be correctly formatted.

Example:

In Qlik Application Automation:

Email received:

Solution

The Send Mail block does not have native support for special characters in the Subject input field, but only supports UTF-8 characters.  To use special characters, a Custom Code block can be used with some PHP code to format the text string to be used by the Subject input field.

Do the following:

1. Create a Custom Code block and place it before the Send Mail block
   
2. Select the Custom Code block and make sure Language is set to PHP 7.4
3. Change one of the default inputs to "Subject" and delete the second default input
4. Paste the following code into the code block, replacing the example code
   

   $subject = $inputs['Subject'];
   $subj = addcslashes(mb_encode_mimeheader($subject, "UTF-8", "Q"), '"');
   echo $subj;
   ?>
   ​

5. Here's the final Custom Code Block
   
   
   
6. Edit the Send Mail block and set Subject input to use the output from the above Custom Code block
   
   
7. Open the Custom Code block and enter the text to be used as a subject in the mail being sent
   
   
8. Run the automation to verify special characters are being correctly formatted in the email subject
   

Environment

• Qlik Application Automation 

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.

Note: These instructions apply to Qlik Cloud. Qlik Sense Enterprise on Windows functions similarly. See How To Edit Published Qlik Sense Apps on Qlik Sense Enterprise on Windows.

Qlik Cloud offers two different spaces to work in. Shared Spaces and Managed Spaces. Apps previously published to a Managed Space e cannot be edited in place, and they will need to be replaced by an app modified on a personal or shared space.

This article covers publishing to both. For additional information on the available space types, see Working in spaces.

• Shared Spaces
• Moving an App to a Shared Space
• Editing in a Shared Space
• Managed Spaces
• Publishing an app to a Managed Space
• Editing a published app in a Management Space
• Replace an app in a Managed Space
• Related Content
• Environment

Shared Spaces

Apps are not published to Shared Spaces. They are moved to or uploaded to them. Apps in shared spaces can therefore be edited freely by anyone that has the correct permissions, like any other unpublished app. Please, check Developing and sharing apps with shared spaces on the help site.

Moving an App to a Shared Space

1. Click the ellipses menu on the app you wish to move
2. Click Move
   
   
   
   
3. Choose the Shared Space you wish to use and click Move
   
   

Editing in a Shared Space

1. Open the app inside the Shared Space
2. If the correct permissions are applied to your account (see Permissions) you will have access to all edit options, such as the Data load editor and Sheet modifications.
   
   You can also publish the App to a Managed Space from inside the Shared Space.
   
   
   

Managed Spaces

Apps cannot be edited directly in managed spaces. The developer will have to modify the original app which is present in their own personal space, or in a shared space. The app is always left in its original place when the app gets published: the publishing process will make a copy of the app, and keep the original where it was.

Publishing an app to a Managed Space

1. Click the ellipses menu on the app you wish to publish
2. Click Publish
   
   
   
   
3. Choose the Managed Space and click Publish
   
   
   
   At this stage, the app is copied. A copy of it will remain in the personal (or shared) space from which you are working. Do not delete this copy.
   

Editing a published app in a Management Space

1. Once published to a Managed Space, the app edit possibilities are reduced to sheet and object creation.
   
   You will not have access to the Data Load Editor, but can still create new sheets, publish/unpublish these sheets, and copy existing sheets.
   
   
   
   
2. If you need to edit the app directly, work on the copy of the app in your personal or shared space and then publish and replace the existing published app.
   
   

   If the original app was deleted at some stage, a published app can be unpublished using the REST API. The developer will then be able to edit the unpublished app.

Replace an app in a Managed Space

1. Click the ellipses menu on the app you wish to publish
2. Click Publish
   
   
   
   
3. Leave Publish new and choose your app. Then click Republish.
   
   
   
   
4. The next step will depend on whether the system is able to identify an existing connection between an unpublished and a published app.
   1. If the system was able to identify a connection, the app will be replaced. If multiple ones are available, choose the app you wish to replace. 

   2. If the system cannot identify a connection (for instance, if the modified app was actually redeveloped from scratch) you will need to manually the space and the exact name of the published app and prompt to replace the app.
      
      

       

       

       

Related Content

Republishing apps

Environment

• Qlik Cloud 

Three requirements need to be met in order to allow Anonymous users access to the Hub:

• The product must not be Qlik Sense Business or Qlik Sense Enterprise SaaS.
• The license must support anonymous access, see Which Qlik Sense Enterprise licenses support anonymous access?
• Proxy must be configured to allow Anonymous users
• A Stream dedicated to anonymous users must be created 

Useful information:

• Users who access Qlik Sense anonymously are identified as NONE\anonymousd9e61933-a7e5-4836-8540-5b137a600e69, where the GUID is a unique identifier.
• To create a license rule, granting login passes to anonymous users you can use two identifiers:
  • userDirectory=NONE 
  • user.IsAnonymous()

Configure the Proxy to allow Anonymous users

By default, anonymous access is disabled. The steps provided require a restart of the Proxy service after completion. 

1. Open the Qlik Sense Management Console.
2. Choose the Virtual Proxy to be used for anonymous access
3. Click Edit.
4. In the Properties menu (right side) choose Authentication
5. From the Anonymous access mode drop-down select Allow anonymous users
   
   
   
   

Set up a license rule 

Anonymous users will need to have a license rule available for them which gives them either an Analyzer Capacity License or a Login Access Token. The instructions in this article will focus on Analyzter Capacity Licenses. 

1. Open the Qlik Sense Management Console.
2. Navigate to License Management 
3. Click Analyzer capacity rules 
4. Click Create new 
5. Give the new rule a Name (mandatory) and Description (optional) 
6. Create one of two possible rules:
   1. In the Basic settings, select
      user: userDirectory =
      value: NONE
      
   2. In the Advanced settings (see Fig 2), provide the condition:
      user.IsAnonymous()
      
      Fig 2

       

7. Click Apply

Set up a Stream for anonymous access

You can use the default Everyone stream, which has already been set up for anonymous access, or create your own. 

We will create two rules. One to allow logged in (authenticated) users access and publishing permissions. One to allow anonymous user access, but no publishing permissons. Note that based on your requirements, this may need to modified. 

1. Go to the Qlik Sense Management Console
2. Go to Manage Content and Streams
3. Click Create New
4. Name your new Stream
5. Click Security Rules 
6. Click Create associated rule (see Fig 2) 
   This will be our "Everyone (anonymous) can read the stream." rule.
   
   Fig 3
7. Provide a Name (mandator) and Description (optional) 
8. In Basic only select Read 
9. In Advanced define
   Condition: user.IsAnonymous()
   Context: Only in hub
   
   See Fig 4. 
   
   Fig 4

    

10. Click Apply 
11. Click Create associated rule (see Fig 2)
    This will be our "Everyone (logged in) can access this stream and publish." rule.
12. Provide a Name (mandator) and Description (optional) 
13. In Basic only select Read and Publish.
14. In Advanced define
    Condition: !user.IsAnonymous()
    Context: Both in hub and QMC
15. Click Apply

Test!

We are now ready to test access. 

1. Go to the Qlik Sense Hub (hosted by the Virtual Proxy you have configured)
2. If you are logged in, log out.
   
   
   
   
3. Our new Anonymous stream is now avaiable.

The reload of the Operations Monitor fails with the following error:

Error: Connector is not responding (System error: ***)

Environment:

Qlik Sense Enterprise on Windows 

The connection query timed out when the default 30 seconds are reached.

Resolution:

1. Open the Qlik Sense Management Console
2. Navigate to Data Connections
3. Change the String Connection of the connection named QLogs from:
   

   CUSTOM CONNECT TO "provider=QvOdbcConnectorPackage.exe;driver=postgres;host=QlikServer1.domain.local;
   port=4432;db=QLogs;FetchTSWTZasTimestamp=1;MaxVarcharSize=262144;"

   to
   

   CUSTOM CONNECT TO "provider=QvOdbcConnectorPackage.exe;driver=postgres;host=QlikServer1.domain.local;
   port=4432;db=QLogs;FetchTSWTZasTimestamp=1;MaxVarcharSize=262144;QueryTimeout=65000;"​

   
   
4. No further action is required. 

The Qlik NPrinting Designer, Engine, and Server version need to be aligned across a deployment.

The versions are not backwards compatible with other components and services on older versions.

Examples:

The Qlik NPrinting Server is on version May 2022. The Qlik NPrinting Designer installed is version February 21.

This is not a supported scenario. 

The Qlik NPrinting Server is on version 17.3.0.0. The designer is on version 17.3.1.1.

This is not a supported scenario.

Environment:

Qlik NPrinting 

Related Content

Can you run different versions of QlikView or Qlik Sense Enterprise on Windows in a cluster or multi node environment? 

All nodes in a QlikView or Qlik Sense Enterprise on Windows environment must be on aligned versions. Having mismatched versions can lead to compatibility issues due to updated features or database changes.

Examples:

A Qlik Sense Enterprise on Windows Central node on February 2022 has two Rim nodes. One Rim node is upgraded to February Patch 9. 

This is not a supported setup.

A QlikView cluster has one node running on April 2020. Another cluster node was upgraded to May 2022.

This is not a supported setup.

Environment

QlikView 
Qlik Sense Enterprise on Windows 

Related Content

Do the Qlik NPrinting Designer, Engine, and Server need to be on the same version? 

Do any Qlik Products (QlikView, Qlik Sense, Qlik NPrinting, etc..) use Microsoft Silverlight?

Environment

• QlikView 
• Qlik Sense Enterprise on Windows 
• Qlik Cloud 
• Qlik NPrinting 

Qlik does not use Microsoft Silverlight in its products. It can be safely uninstalled without risking functionality.

Please see our Third Party Terms for details on what third-party software Qlik works with.

Accessing a .CSV file with the Qlik Sense Web File Connector fails with Service is Unavailable

The Qlik Sense Engine logs read:

ERROR        QlikServer1        0210df73-0c1e-4157-8b84-e90fbbc541f8        20220201T172702.490+0100        12.878.15.0        Command=Doc::CreateConnection;Result=503;ResultText=Error: Service Unavailable        87723a64-7f75-4d20-b878-c4aa94b33cff        1f94a9d3-d453-45a0-a359-ab95d5c2f0f4        56        DOMAIN        qvservice        c29abc66-f3fc-4a55-bb85-0610324cbc14        21595c90-f4ef-4384-ad20-04bf85c35df5        Web File Test        Engine        Not available        Doc::CreateConnection        Doc::CreateConnection        503        A connection with the server could not be established

The engine trace logs read:

ERROR        QlikServer1        System.Engine.Engine        86        fed3689f-5ea3-4f2d-9bfa-c02fca21769a        DOMAIN\qvservice        Webfile Connector: Failed to get the IP address of www.xxxxxx.com 

Environment

Qlik Sense Enterprise on Windows 

Can affect: June 2020, September 2020, November 2020, February 2021 as well as upgrades from these versions. 

Does not affect: Fresh Installs of Qlik Sense May 2021, August 2021, or November 2021 versions as well as any later releases.

Resolution

1. Stop the Qlik Sense Engine Service.
2. In the [Settings 7] section in Settings.ini, add the setting WebFileUseWinAPI=0
   
   

   [Settings 7] 
   WebFileUseWinAPI=0

   
   In both Qlikview and Qlik Sense, setting the settings.ini WebFileUseWinAPI = 1 will activate the old way of handling web files which use Windows APIs instead of libcurl and lets Windows handle the proxy redirecting. Since the internet proxy is bypassed using libcurl it is useful to activate this setting if you require the web traffic to go through the proxy.
   
   
   For instructions on how to edit the settings.ini file see How to modify Qlik Sense Engine's Settings.ini.
   
   
3. Start the Engine Service.

Fix Version:

The February 2022 release (and later) changes to libcurl mode as the default mode for web files, mitigating this issue without the need to set the workaround in the settings.ini.

In previous versions, the possibility to switch to libcurl mode exists through the settings.ini. 

Internal Investigation ID(s):

QB-8941

When we have more than 500 entities in the project and try to reference an existing entity in the Data Mart it does not show up.

Environment

Qlik Compose 

Cause 

This is because there is a parameter only visible in the JSON which has a limit set at 500.

Resolution

1. Create the deployment package for the project.
2. Open the zip file generated and edit the project.json
3. Search for the parameter max_number_of_entities_in_tree_nodes
4. The default value is 500.  Increase it to 1000 or the maximum number of entities in the project.
5. Save the file and import the modified deployment package on top of the existing project.
6. Since this is only visible at the JSON level, once we import the deployment package we will have to rebuild all the task statements again which is an additional effort.

This article gives an overview of the available blocks in the DataRobot connector in Qlik Application Automation. It will also go over some basic examples of retrieving deployments and predictions from that deployment within a DataRobot account.

This connector supports LIST and GET operations for the following modules in DataRobot:

• deployments
• predictions
• dedicated predictions

List of Blocks in DataRobot

1. Get Deployment
2. Get Deployement Service Statistics
3. List Deployments
4. List Prediction Explanation From Dedicated Prediction API
5. List Predictions
6. List Predictions From Dedicated Prediction API
7. List Time Series Predictions From Dedictaed Predictions API
8. Raw API Request Endpoints(Get,List,Patch,Post,Put,Delete)

You can use the Dedicated Prediction API blocks(List Predictions From Dedicated Prediction API,List Prediction Explanation From Dedicated Prediction API,List Time Series Predictions From Dedictaed Predictions API) to get the predictions from your dedicated prediction instance. You will need your dedicated prediction url , deployment ID and DataRobot Key(in case of Managed AI Cloud User) to get results from those blocks.

Authentication

Authentication for this connector is based on the API Key . You can find the API Key once you go to Profile->Developer Tools->API Keys in your DataRobot account.

Let's now go over a few basic examples of how to use the DataRobot connector:

1. How to list deployments from a DataRobot account:

1. Create an automation.
2. From the left menu, select the DataRobot connector.
   
3. Use the 'Search for blocks' input to search for the "list deployments' block.
   
4. Drag and drop the block into the automation and link it to the start block.
   
5. From the left menu, search for the 'Output' block.
   
6. Drag and drop the 'output' block into the automation and link it to the 'List deployments' block.
   
7. Run the automation (if not saved previously, a 'Save automation' popup will appear). This will output a paginated list of deployments available.

2. How to list predictions from a dedicated predictions API in the DataRobot account:

1. The first two steps are similar as before.
2. Create a JSON List of the data to be predicted. For more information on creating JSON List in an automation, refer this article .
   
3. Use the 'Search for blocks' input to search for the 'List Predictions From Dedicated Prediction API' block.
4. Drag and drop the block into the automation and link it below the variable blocks.
   
5. On the right side of the screen, use the input fields to fill in the deployment information. You can find the information on getting the DataRobot key here .
   
6. Drag and link an output block inside the loop of "List Predictions From Dedicated Prediction API" block.
   
7. Run the automation (if not saved previously, a 'Save automation' popup will appear). This will get the predictions for your provided data from the deployed model in your DataRobot account and output this information.

Simiarly you can make use of other blocks to get the predictions and other information from DataRobot.

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

This article provides an overview of getting started with the Swapcard Connector in Qlik Application Automation.

Swapcard is the leading event & community platform when it comes to running large and complex in-person, hybrid and virtual events. Leverage Swapcard's AI and matchmaking modules to engage your audience & generate leads for exhibitors and sponsors.

Adding the Connection in QAA

To get started with Swapcard you need an API token, go to API keys option under the top-right menu icon here. Or Contact dev@swapcard.com to request your personal API token.
For more info, see Getting started - Swapcard Developer

Once you have the API token, connect to the data source using the API token.

Working with Swapcard blocks

To work with the blocks in QAA, select the connector on the left and either scroll through the list, choose the filter, or type the name in the search box to find the endpoint block you want to use.

To access tasks data, the following endpoints are currently supported:

1. List events
2. List Exhibitors
3. Add Or Update Exhibitors
4. List Groups by Event Id
5. Add Group To Person
6. Remove groups from person
7. list people
8. add person
9. update person
10. delete person
11. add barcode to person
12. update person barcode
13. Add member to exhibitor
14. get person
15. get person by email
16. remove person custom field values

Help text on some fields 

Custom fields 

Custom fields are values we add to an object which was not amongst the existing options preconfigured.
More information can be found on articles like this.
Example Use Case - For “Remove Person Custom Field Values” you need to enter the custom field id and the necessary details for the field of interest. The then selected custom field id will be removed form that person, and should reflect in dashboard.

Extra fields 

Use of “extra fields” in list and get endpoints – you can refer the GraphQL documentation and add any fields in the output, that are not already present.

The only format needed here is to copy paste exactly how the explorer writes the query when you select your field of interest, so if it is a direct field it’ll be a straightforward value like – description.

And in case of a child and child object like city you will have - address {city country}

Ever wanted to brand or customize the default Qlik Sense Login page?

The functionality exists, and it's really as simple as just designing your HTML page and 'POSTing' it into your environment.

We've all seen the standard Qlik Sense Login page, this article is all about customizing this page.

To customize the page:

1. We highly recommend setting up a new virtual proxy with Forms so you don't impact any users that are using auto-login Windows auth.
   
   Example setup:
   
   Description: Custom Forms Page
   Prefix: customlogin
   Session cookie header-name: X-Qlik-Session-CustomLogin
   Windows authentication pattern: Forms
   
   
   
   
2. Once this is done, a good starting point is to download the default login page.
   
   You can open up your web developer tool of choice, go to the login page, and download the HTML response from the GET http://<server>/customlogin/internal_forms_authentication request. It should be roughly a 273 line .html file.
   
   
3. Once you have this file, you can more or less customize it as much as you'd like.
   
   Image files can be inlined as you'll see in the qlik default file, or can be referenced as long as they are publicly accessible. The only thing that NEEDS to exist are the input boxes with appropriate classes and attributes, and the 'Log In' button.
   
   
4. After building out your custom HTML page and it looks great, it needs to be converted to Base64. There are online tools to do this, openssl also has this functionality.
   
   
5. Once you HAVE your Base64 encoded HTML file, then you will want to PUT it into your sense environment.
   
   First, do a GET request  on /qrs/proxyservice and find the ID of the proxy service you want this login page to be shown for.
   
   You will then do a GET request on /qrs/proxyservice/<id> and copy the body of that response. Below is an example of that response.
   
   

   {
       "id": "8817d7ab-e9b2-4816-8332-f8cb869b27c2",
       "createdDate": "2020-03-23T15:39:33.540Z",
       "modifiedDate": "2020-05-20T18:46:13.995Z",
       "modifiedByUserName": "INTERNAL\\sa_api",
       "customProperties": [],
       "settings": {
           "id": "8817d7ab-e9b2-4816-8332-f8cb869b27c2",
           "createdDate": "2020-03-23T15:39:33.540Z",
           "modifiedDate": "2020-05-20T18:46:13.995Z",
           "modifiedByUserName": "INTERNAL\\sa_api",
           "listenPort": 443,
           "allowHttp": true,
           "unencryptedListenPort": 80,
           "authenticationListenPort": 4244,
           "kerberosAuthentication": false,
           "unencryptedAuthenticationListenPort": 4248,
           "sslBrowserCertificateThumbprint": "e6ee6df78f9afb22db8252cbeb8ad1646fa14142",
           "keepAliveTimeoutSeconds": 10,
           "maxHeaderSizeBytes": 16384,
           "maxHeaderLines": 100,
           "logVerbosity": {
               "id": "8817d7ab-e9b2-4816-8332-f8cb869b27c2",
               "createdDate": "2020-03-23T15:39:33.540Z",
               "modifiedDate": "2020-05-20T18:46:13.995Z",
               "modifiedByUserName": "INTERNAL\\sa_api",
               "logVerbosityAuditActivity": 4,
               "logVerbosityAuditSecurity": 4,
               "logVerbosityService": 4,
               "logVerbosityAudit": 4,
               "logVerbosityPerformance": 4,
               "logVerbositySecurity": 4,
               "logVerbositySystem": 4,
               "schemaPath": "ProxyService.Settings.LogVerbosity"
           },
           "useWsTrace": false,
           "performanceLoggingInterval": 5,
           "restListenPort": 4243,
           "virtualProxies": [
               {
                   "id": "58d03102-656f-4075-a436-056d81144c1f",
                   "prefix": "",
                   "description": "Central Proxy (Default)",
                   "authenticationModuleRedirectUri": "",
                   "sessionModuleBaseUri": "",
                   "loadBalancingModuleBaseUri": "",
                   "useStickyLoadBalancing": false,
                   "loadBalancingServerNodes": [
                       {
                           "id": "f1d26a45-b0dd-4be1-91d0-34c698e18047",
                           "name": "Central",
                           "hostName": "qlikdemo",
                           "temporaryfilepath": "C:\\Users\\qservice\\AppData\\Local\\Temp\\",
                           "roles": [
                               {
                                   "id": "2a6a0d52-9bb4-4e74-b2b2-b597fa4e4470",
                                   "definition": 0,
                                   "privileges": null
                               },
                               {
                                   "id": "d2c56b7b-43fd-44ad-a12f-59e778ce575a",
                                   "definition": 1,
                                   "privileges": null
                               },
                               {
                                   "id": "37244424-96ae-4fe5-9522-088a0e9679e3",
                                   "definition": 2,
                                   "privileges": null
                               },
                               {
                                   "id": "b770516e-fe8a-43a8-a7a4-318984ee4bd6",
                                   "definition": 3,
                                   "privileges": null
                               },
                               {
                                   "id": "998b7df8-195f-4382-af18-4e0c023e7f1c",
                                   "definition": 4,
                                   "privileges": null
                               },
                               {
                                   "id": "2a5325f4-649b-4147-b0b1-f568be1988aa",
                                   "definition": 5,
                                   "privileges": null
                               }
                           ],
                           "serviceCluster": {
                               "id": "b07fc5f2-f09e-4676-9de6-7d73f637b962",
                               "name": "ServiceCluster",
                               "privileges": null
                           },
                           "privileges": null
                       }
                   ],
                   "authenticationMethod": 0,
                   "headerAuthenticationMode": 0,
                   "headerAuthenticationHeaderName": "",
                   "headerAuthenticationStaticUserDirectory": "",
                   "headerAuthenticationDynamicUserDirectory": "",
                   "anonymousAccessMode": 0,
                   "windowsAuthenticationEnabledDevicePattern": "Windows",
                   "sessionCookieHeaderName": "X-Qlik-Session",
                   "sessionCookieDomain": "",
                   "additionalResponseHeaders": "",
                   "sessionInactivityTimeout": 30,
                   "extendedSecurityEnvironment": false,
                   "websocketCrossOriginWhiteList": [
                       "qlikdemo",
                       "qlikdemo.local",
                       "qlikdemo.paris.lan"
                   ],
                   "defaultVirtualProxy": true,
                   "tags": [],
                   "samlMetadataIdP": "",
                   "samlHostUri": "",
                   "samlEntityId": "",
                   "samlAttributeUserId": "",
                   "samlAttributeUserDirectory": "",
                   "samlAttributeSigningAlgorithm": 0,
                   "samlAttributeMap": [],
                   "jwtAttributeUserId": "",
                   "jwtAttributeUserDirectory": "",
                   "jwtAudience": "",
                   "jwtPublicKeyCertificate": "",
                   "jwtAttributeMap": [],
                   "magicLinkHostUri": "",
                   "magicLinkFriendlyName": "",
                   "samlSlo": false,
                   "privileges": null
               },
               {
                   "id": "a8b561ec-f4dc-48a1-8bf1-94772d9aa6cc",
                   "prefix": "header",
                   "description": "header",
                   "authenticationModuleRedirectUri": "",
                   "sessionModuleBaseUri": "",
                   "loadBalancingModuleBaseUri": "",
                   "useStickyLoadBalancing": false,
                   "loadBalancingServerNodes": [
                       {
                           "id": "f1d26a45-b0dd-4be1-91d0-34c698e18047",
                           "name": "Central",
                           "hostName": "qlikdemo",
                           "temporaryfilepath": "C:\\Users\\qservice\\AppData\\Local\\Temp\\",
                           "roles": [
                               {
                                   "id": "2a6a0d52-9bb4-4e74-b2b2-b597fa4e4470",
                                   "definition": 0,
                                   "privileges": null
                               },
                               {
                                   "id": "d2c56b7b-43fd-44ad-a12f-59e778ce575a",
                                   "definition": 1,
                                   "privileges": null
                               },
                               {
                                   "id": "37244424-96ae-4fe5-9522-088a0e9679e3",
                                   "definition": 2,
                                   "privileges": null
                               },
                               {
                                   "id": "b770516e-fe8a-43a8-a7a4-318984ee4bd6",
                                   "definition": 3,
                                   "privileges": null
                               },
                               {
                                   "id": "998b7df8-195f-4382-af18-4e0c023e7f1c",
                                   "definition": 4,
                                   "privileges": null
                               },
                               {
                                   "id": "2a5325f4-649b-4147-b0b1-f568be1988aa",
                                   "definition": 5,
                                   "privileges": null
                               }
                           ],
                           "serviceCluster": {
                               "id": "b07fc5f2-f09e-4676-9de6-7d73f637b962",
                               "name": "ServiceCluster",
                               "privileges": null
                           },
                           "privileges": null
                       }
                   ],
                   "authenticationMethod": 1,
                   "headerAuthenticationMode": 1,
                   "headerAuthenticationHeaderName": "userid",
                   "headerAuthenticationStaticUserDirectory": "QLIKDEMO",
                   "headerAuthenticationDynamicUserDirectory": "",
                   "anonymousAccessMode": 0,
                   "windowsAuthenticationEnabledDevicePattern": "Windows",
                   "sessionCookieHeaderName": "X-Qlik-Session-Header",
                   "sessionCookieDomain": "",
                   "additionalResponseHeaders": "",
                   "sessionInactivityTimeout": 30,
                   "extendedSecurityEnvironment": false,
                   "websocketCrossOriginWhiteList": [
                       "qlikdemo",
                       "qlikdemo.local"
                   ],
                   "defaultVirtualProxy": false,
                   "tags": [],
                   "samlMetadataIdP": "",
                   "samlHostUri": "",
                   "samlEntityId": "",
                   "samlAttributeUserId": "",
                   "samlAttributeUserDirectory": "",
                   "samlAttributeSigningAlgorithm": 0,
                   "samlAttributeMap": [],
                   "jwtAttributeUserId": "",
                   "jwtAttributeUserDirectory": "",
                   "jwtAudience": "",
                   "jwtPublicKeyCertificate": "",
                   "jwtAttributeMap": [],
                   "magicLinkHostUri": "",
                   "magicLinkFriendlyName": "",
                   "samlSlo": false,
                   "privileges": null
               }
           ],
           "formAuthenticationPageTemplate": "",
           "loggedOutPageTemplate": "",
           "errorPageTemplate": "",
           "schemaPath": "ProxyService.Settings"
       },
       "serverNodeConfiguration": {
           "id": "f1d26a45-b0dd-4be1-91d0-34c698e18047",
           "name": "Central",
           "hostName": "qlikdemo",
           "temporaryfilepath": "C:\\Users\\qservice\\AppData\\Local\\Temp\\",
           "roles": [
               {
                   "id": "2a6a0d52-9bb4-4e74-b2b2-b597fa4e4470",
                   "definition": 0,
                   "privileges": null
               },
               {
                   "id": "d2c56b7b-43fd-44ad-a12f-59e778ce575a",
                   "definition": 1,
                   "privileges": null
               },
               {
                   "id": "37244424-96ae-4fe5-9522-088a0e9679e3",
                   "definition": 2,
                   "privileges": null
               },
               {
                   "id": "b770516e-fe8a-43a8-a7a4-318984ee4bd6",
                   "definition": 3,
                   "privileges": null
               },
               {
                   "id": "998b7df8-195f-4382-af18-4e0c023e7f1c",
                   "definition": 4,
                   "privileges": null
               },
               {
                   "id": "2a5325f4-649b-4147-b0b1-f568be1988aa",
                   "definition": 5,
                   "privileges": null
               }
           ],
           "serviceCluster": {
               "id": "b07fc5f2-f09e-4676-9de6-7d73f637b962",
               "name": "ServiceCluster",
               "privileges": null
           },
           "privileges": null
       },
       "tags": [],
       "privileges": null,
       "schemaPath": "ProxyService"
   }

    

6. You can then take your base64 encoded HTML file, paste that value into the 'formAuthenticationPageTemplate' field.
   
   Once you have an updated body, you can use the PUT verb (with an updated modifiedDate) to PUT this body back into the repository. Once this is done, you should be able to goto your virtual proxy and you should see your new login page (very Qlik branded in this example):
   
   
   
   

If your login page does NOT work, you can simply do a GET call on your proxy service, and set formAuthenticationPageTemplate back to an empty string:

formAuthenticationPageTemplate": ""

Once this is done, you should get reverted back to the default login screen.

Environment:

Qlik Sense Enterprise on Windows 

By default, QlikView Publisher sets the number of "Max number of QlikView engines to use for distribution" to 4. This value determines how many QlikView Publisher tasks can be run in parallel and can be freely adjusted to suit any environment. Sometimes you see the error/warning Failed to allocate engine before you hit the limit you have set.  

A more detailed best practice guide is available in Scaling the QlikView Publisher.
 

The image below depicts where to increase the number of engines for distribution or administration. (default 4 and 20 respectively)

When determining how many Reload Engines to allow per QlikView Publisher, there are a number of factors to take into consideration. 

Fully MultiThreaded

The first and fundamental factor that affects how many Reloads that can safely take place simultaneously, is that the Reload Engine, the QVB.exe process, is a fully MultiThreaded process. This means that a single executing task using a Reload Engine WILL try to use as much resources from the hardware as it can, without limit. The limiting factors are only Script Efficiency and Data transfer rates. A reload script that does lots of data aggregation at script level will have a big impact on the CPU utilization for that Reload Task for example. Tasks that run in parallel on a server will compete for the same pool of resources containing CPU cycles and RAM. 

With this basic fundamental factor in mind, we can start discussing the possible settings

The first consideration is that you should never allow for more Engines than the Server has CPU cores -1. So for a Server with 8 CPU cores, we should never sat a value higher than 7. 

Note also, that the QlikView Distribution Service has been equipped with a load protection mechanism since the 12.10 release. See Tasks are not executed as expected and are shown in status Queued for details. 
 

System bottlenecks

The second consideration is that even on big servers with lots of CPU cores (16+) it rarely pays to go higher than approximately 13 simultaneous reload engines allowed. This is partly due to the first fundamental factor (every running task will try to consume all the resources) and partly due to other bottlenecks, where for example multiple data connections using the same drive will start becoming slower as the concurrent connections goes up. Going for a high number also normally increases the failure rate significantly. Qlik recommends starting with a low number and then increasing gradually until you hit the sweet-spot for your own environment, where you are getting a high throughput without introducing a high failure rate. If your reload schedule calls for a high number of simultaneous tasks to execute, you will be better off clustering the Publisher role over more servers than increasing the number of engines on a single node. 
 

Windows limitation

A third consideration is Windows settings that affect the number of concurrent processes of the same kind. If you enable a high number of reload engines and start seeing windows errors related to Windows running out of Desktop Heap Size. This may be visible in the Windows System Event log of the server running Qlikview Distribution Service, with errors saying "Desktop Heap exhausted". If so, you will need to adjust Windows Desktop Heap Size to allow for a higher server load. Allowing for a bigger Desktop Heap may also allow a highly loaded server to run for longer periods of time without the need for server restarts.
Messages like this,
Failed to create QlikView Engine.. Exception=System.Runtime.InteropServices.COMException (0x80080005)
Shows that there is an issue with desktop heap size.

IMPORTANT: Windows registry changes are made at your own risk and are not supported by Qlik Support. Please make a backup of the Windows registry before applying changes to enable rollback if the setting change fails or introduces Windows instability.

Desktop Memory Heap size is control in the following Windows registry key on the server running Qlikview Distribution Service:

Change the desktop heap setting by setting the SharedSection value to 1024,20480,2048. After change the registry key should look something like the following (all on one line):

%SystemRoot%\system32\csrss.exe ObjectDirectory=\Windows SharedSection=1024,20480,2048 ...

Notice that the default value is 1024,3072,512 in x86 or 1024,20480,768 in x64 environments. 
Also, please note that the skipped part (marked as "..." ) might differ according to the operating system version and should not be modified.

Depending on size of deployment and complexity of tasks/scripts you might need to increase the Non-interactive Desktop Heap even further, the following list gives the next possible setting for the value. 

%SystemRoot%\system32\csrss.exe ObjectDirectory=\Windows SharedSection=1024,20480,4096 ...

OR

%SystemRoot%\system32\csrss.exe ObjectDirectory=\Windows SharedSection=1024,20480,6144 ...

OR

%SystemRoot%\system32\csrss.exe ObjectDirectory=\Windows SharedSection=1024,20480,8192 ...

Microsoft reference regarding Windows heap and Server 2012: https://support.microsoft.com/en-us/kb/947246
 

A more detailed best practice guide is available in Scaling the QlikView Publisher.

Update Aug. 4, 2022 12:00 EST:

This issue has been resolved.

If your account was locked due to multiple login attempts, please follow My Qlik Account is blocked - Your Account has been blocked after multiple login attempts after the backend issue has been resolved. 

One of the following errors can be seen when attempting to log in to your Qlik Cloud tenant:

{"errors":[{"title":"Authentication failed. Error received from identity provider","code":"LOGIN-3","status":"401"

We're sorry. Something went wrong while processing your request. Please try again.

YOUR ACCOUNT HAS BEEN BLOCKED AFTER MULTIPLE CONSECUTIVE LOGIN ATTEMPTS

Our team has identified and resolved an issue with one of our technical partners that is impacting Qlik cloud sign-ins and registrations via Qlik IDP. 

See our status page for details.

A Qlik Sense reload task is stuck in the Triggered state. All services are otherwise running and other tasks are executing and finishing correctly. 

Reviewing the Qlik Sense Scheduler logs shows:

Execution session found during resume is not running in any slave scheduler and will be deleted

and/or

Unexpected exception in Delete for Entity ExecutionSession with Id < >

Resolution

1. Change the scheduler settings in Qlik Management Console to Manager and Worker (Not necessary in Single node)
2. Stop all the Qlik Sense Services except the Repository database service
3. Make a backup of the Repository database: How to backup PostgreSQL database in Qlik Sense.
4. Locate pgAdmin or install it. Installing and Configuring PGAdmin 4 to access the PostgreSQL database used by Qlik Sense or NPrinting
5. Open and Log in to PGAdmin
6. Login to (newly added) Qlik Sense Server in PGAdmin
7. Expand QSR Database
8. Find and Open the ExecutionSessions table
   
   
   
   
9. Right Click - View/Edit Data - All Rows in the ExecutionSessions table or Open Query Tool and Run the below query:
   

   SELECT 
     "ExecutionSessions"."ID", 
     "ExecutionSessions"."AbortAt", 
     "ExecutionSessions"."Retries", 
     "ExecutionSessions"."AbortReason", 
     "ExecutionSessions"."User", 
     "ExecutionSessions"."CreatedDate", 
     "ExecutionSessions"."ModifiedDate", 
     "ExecutionSessions"."SyncDate", 
     "ExecutionSessions"."ModifiedByUserName", 
     "ExecutionSessions"."App_ID", 
     "ExecutionSessions"."ExecutingNode_ID", 
     "ExecutionSessions"."ExecutionResult_ID", 
     "ExecutionSessions"."ReloadTask_ID", 
     "ExecutionSessions"."UserSyncTask_ID", 
     "ExecutionSessions"."ExternalProgramTask_ID"
   FROM 
     public."ExecutionSessions";

10. If you get any errors as below, delete that entry and Run the query again.
    

    ERROR:  syntax error at or near ""ExecutionSessions""
    LINE 1:   "ExecutionSessions"."SyncDate", 
              ^
    SQL state: 42601
    Character: 3

11. Wipe the data from the ExecutionSessions table. See SQL statements below.
    
    Please note that this will need to be a hard deletion from the table and not soft deletion. For this, run the below Query;
    

    DELETE 
    FROM 
    public."ExecutionSessions";​

12. Restart the QlikSense Server ( full reboot ).
13. After the reboot, start the Qlik Sense services (if not already started) and try running the tasks again.

Cause

Corruption may occur due to:

1. A row that is incomplete ( blank values ) in the ExecutionSessions table data
2. ID reference to a task that does not exist anymore
3. Entries flagged as incomplete that interfere with the execution queue ( block the next tasks )
4. Entries with IDs that already exist in the table, and new entries with the same ID will cause an error and abort the execution

This can look like this in the repository database:

Environment

• Qlik Sense Enterprise on Windows All the versions

1. An implementation of ISessionProvider is complaining about a thread being already blocked by a session when a session shall be activated.
2. Communication does not work at all showing error messages referring to NI.
3. An exception occurs that is similar to: SAP.Middleware.Connector.RfcInvalidParameterException: Element ABC of container metadata XYZ unknown
   

   at SAP.Middleware.Connector.RfcContainerMetadata.NameToIndex(String elementName)
   at SAP.Middleware.Connector.RfcXRfcParser.ProcessBeginTag()
   at SAP.Middleware.Connector.RfcXRfcParser.parse()​

4. An exception occurs that is similar to: SAP.Middleware.Connector.RfcInvalidStateException: index 30 out of range
5. A parameter of type BYTE is truncated.
   An exception occurs that is similar to: System.ArgumentNullException: Value cannot be null. Parameter name: args
   

   at String.Format(IFormatProvider provider, String format, Object[] args)
   at TextWriter.WriteLine(String format, Object[] arg)
   at RfcTrace.set_TracePerThread(Boolean perThread)​

Other Terms

RFC_METADA_GET, EX_FUNCTIONS

Reason and Prerequisites

The problems above have been caused by the following issues in NCo 3.0.23:

1. The session was created within an NCo Server. A critical error situation occurred, which caused the connection to be closed. As RFC sessions are associated with the connection, the session implicitly ended, but the registered ISessionProvider was not notified about this.
2. NI is the socket layer used by NCo. Under certain circumstances, it could happen that the initialization routine is not invoked before using the sockets.
3. The function module invoked returns a table or a nested structure in an exporting parameter, which is not defined in the metadata used for that function module. When trying to process the received data, the unknown parameter should be accessed, which led to the exception.
4. The function module invoked returns a table or a nested structure in an exporting parameter and the data amount is huge. In some border cases, the mentioned exception could occur.
5. The metadata retrieved for that function parameter was interpreted incorrectly so that the data was truncated at half the size.
6. Tracing policy is switched after traces were already written.

Resolution

Upgrade to at least NCo 3.0.24, which is available on the download page under SAP Connector for Microsoft .NET, or download

"Qlik Connector for use with SAP NetWeaver(R) v8.0.1" which contains 3.0.24 from the Qlik Downloads site.

Please note that this is a patch level exclusively for the .NET 4.0 binaries, specifically for the .NET runtime 4.0, 4.5, 4.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2, or 4.8. For the .NET 2.0 binaries support ended on July 31, 2018.

1. Also in case of exceptions, the ISessionProvider is notified about a destroyed session.
2. NCo ensures that the initialization happens very early.
3. Unknown parameters are now always ignored.
4. The border cases are now treated correctly.
5. Metadata interpretation has been corrected for BYTE parameters.
6. Tracing policy switch was corrected.

In addition, the following enhancements have been added:

1. Improved tracing of the invocations for the methods of the registered ISessionProvider of RfcSessionManager.
2. Suppressing dev_nco_rfc.log when changing trace directory unless log has already been written to it.

Environment

Qlik SAP Connectors 

QlikView throws the below error while testing the SapSQL Connection:

Connection failed

RfcCommunicationException: The only destination DefaultDestination available failed when retrieving metadata from ESS -- see log for details

Below error found in SAP SQL Connector logs files (C:\ProgramData\QlikTech\Custom Data\QvSAPSqlConnector\Log\)

SqlSapService.OpenConnection() - Using SocketBufferSize:32768

Connection to SAP verified, using sapnco version:3.0.18.0 with SocketBufferSize:32768

Mismatch Error in SapErpConnection.TransportsHaveCorrectVersion(): RfcCommunicationException:The only destination DefaultDestination available failed when retrieving metadata from ESS -- see log for details 

Environment

• QlikView All versions
• Qlik SAP Connectors 8.0.0 or earlier versions

Resolution

1. You must be on the recent .NET Framework version.
2. Upgrade to SAP Connector version to 8.0.1 as this is a known issue found in earlier versions of 3.0.24.
   • SAP .NET connector version is 3.0.24 is included in 8.0.1 and be confirmed in details of "sapnco.dll" found in "C:\Program Files\Common Files\QlikTech\Custom Data\QvSAPSqlConnector\"

Cause

The problems above have been caused by the following issues in NCo 3.0.23:

1. The session was created within an NCo Server. A critical error situation occurred, which caused the connection to be closed. As RFC sessions are associated with the connection, the session implicitly ended, but the registered ISessionProvider was not notified about this.
2. NI is the socket layer used by NCo. Under certain circumstances, it could happen that the initialization routine is not invoked before using the sockets.
3. The function module invoked returns a table or a nested structure in an exporting parameter, which is not defined in the metadata used for that function module. When trying to process the received data, the unknown parameter should be accessed, which led to the exception.
4. The function module invoked returns a table or a nested structure in an exporting parameter and the data amount is huge. In some border cases, the mentioned exception could occur.
5. The metadata retrieved for that function parameter was interpreted incorrectly so that the data was truncated at half the size.
6. Tracing policy is switched after traces were already written.

Related Content 

Known Issues - SAP .NET Connector Version 3.0.23 and previous Versions - Qlik Connector for use with SAP NetWeaver(R) 

Not able to create a connection to Azure Blob Storage from Qlik Azure connector in Qlik Sense SaaS

Qlik Sense throws the below error while connecting to the "Azure Storage" Connector:

HttpStatusCode: Unauthorized, StatusCode: 401, StatusDescription: Server failed to authenticate the request.

Environment

• Qlik Cloud 
• Qlik Sense Business 

Resolution

A good walkthrough of configuring Azure Blob Storage for access by Qlik Cloud can be found here:

Configuring Azure Blob Storage in Qlik SaaS (Qlik Cloud Services, Qlik Sense Business)

1. Double-check all param values (make sure no leading/trailing whitespace just in case) and also that the user has these permissions:
   • Storage Blob Data Owner
   • Storage Blob Data Contributor
   • Storage Blob Data Reader
2. Check/Test connecting via another method, e.g: via Azure Storage Explorer (just to validate permissions, etc.,) 
3. Check the "Networking" setting under your Storage Account in the Azure portal if  "Enabled from selected virtual networks and IP addresses" is enabled.
   • If yes, you must Allowlist the IP Addresses for the Qlik Cloud Region.
4. You must use the "User Principal Name" to create the Azure connection

Related Content

AuthorizationPermissionMismatch Error 403 with Azure blob storage and Qlik Sense Enterprise SaaS and Qlik Sense Enterprise Business 

License error while connecting Microsoft Teams through Insight Advisor Chat in Qlik Sense.

Insight Advisor Chat works fine inside the Qlik Sense but after the configuration with an external Chatbot like Microsoft Teams, the below error appears:

Error: License is invalid or expired. Please contact your administrator.

In NLAppSearch logs:

{"caller":"enterprise.go:72","environment":"localdev","level":"info","message":"License is valid. Enabling event listeners","timestamp":"2022-07-29T04:55:30.8725058Z","version":"1.31.3"}
{"caller":"qsmq-msgbroker.go:161","environment":"localdev","level":"error","message":"failed queuesubscribe on an unsupported subject","subject":"system-events.tenants","timestamp":"2022-07-29T04:55:40.8430957Z","version":"1.31.3"}

Whereas in bot-channel-service logs:

2022-07-29T10:36:12.723Z [index] info: License is invalid or expired. Please contact your administrator.

Environment

• Qlik Sense Enterprise on Windows 

Resolution

The below attributes must be present in the License LEF  in order to use Chatbots like Skype, Team, Slack, etc with Insight Advisor Chat

CHANNELS;YES;;

INSIGHTBOT;YES;;<VALID_DATE>

Note: InsightBot is being rebranded as Insight Advisor Chat and the new attribute supports the rebranding. Qlik Sense Version November 2020 onward supports both the new Insight Advisor Chat and the old (Insight Bot) attribute.

Cause

• CHANNELS or INSIGHTBOT attribute is not present in the License LEF
• CHANNELS or INSIGHTBOT  attribute is set to NO
• INSIGHTBOT's License has expired

Related Content

Configuring Qlik Insight Advisor Chat for external channels 
Configuring the communication channel for Microsoft Teams 

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.

Environment

• Qlik Replicate 

Introduction

When larger tables participate in the Full Load replication phase in Qlik Replicate, you can accelerate the replication of these tables by splitting them into logical segments and loading these segments in parallel. Tables can be segmented by data ranges, by partitions, or by sub-partitions. 

This article provides guidance in finding the adequate data segment boundaries based on actual data stored in those tables on the source.

Size does matter

As a first step, it is essentially to understand the size of the data tables.

Not every long table is big, nor not every short table is small. Table average uncompressed data size is determined by the formula below:

“table_size_MB” = “number of records in the table” * “avg. record length”

The table size may directly affect the unload duration. The longer is the unload, the bigger impact it will have on the following:

• Source transactional concurrency – may cause locking on the source
• Number of cached changes to apply on the target during the FL + CDC process
• Overall duration of a Full Load process

It is a good practice to unload the source table in “digestible” chunks that could be loaded optimally in less than 30 minutes. The amount of data in each segment can vary between tens of MB and few GBs and will heavily depend on the network quality and bandwidth, source database load at any given time, source database processing capability and other environmental aspects. The best way to gauge the overall  Full Load performance  is to test how long it takes to Full Load for a medium size table in your environment, and  extrapolate from there.

Each segment should contain a reasonable number of records.  Depending on the table width, the “reasonable” number of records in each batch may vary. As a rule of thumb, we would want each partition\segment load duration to be in a ballpark of 15-30 minutes.

This is important for the following reasons:

• to avoid any contention in the source DB
• to prevent the thread from being dropped because of excessive duration by either
  • TCP layer
  • ODBC driver itself
  • source DB

Calculating the “partition” size

At this point we assume that we already know the approx. number of logical “partitions” (or segments) we would want to use for parallel unload. Perform the following to calculate the partition size:

1. To obtain the estimated number of rows for each logical partition [records_in_logpart] get the table row count from the system catalog or count(*) from the table itself and divide this number by number of parallel load processes you want to create.
2. Adjust the queries below to the table, where:
   1. SCHEMA.TABLE – qualified identifier of a production table name
   2. COL1PK, COL2PK,…,COLnPK – represent the Primary Key columns in the order they appear in the index itself.
   3. the columns should be the ones you are going to partition by, and the [records_in_logpart] represents the number calculated in the previous step

NOTE – when identifying the data ranges for SAP tables, MANDT field should appear in the subqueries  WHERE clause 

ORACLE:

SELECT T1.GEN1, T1.THIS_ROW
FROM (
    SELECT GEN1, ROWNUM  AS THIS_ROW
    FROM (
        SELECT CAST(COL1PK AS VARCHAR(200))||';'||CAST(COL2PK AS VARCHAR(200)) AS GEN1
        FROM SCHEMA.TABLE
        ORDER BY COL1PK, COL2PK DESC
         )
      ) AS T1
WHERE MOD(T1.THIS_ROW, [records_in_logpart]) = 0;

DB2i / DB2LUW / DB2z:

SELECT T1.GEN1, T1.THIS_ROW
FROM (
    SELECT
    ROW_NUMBER() OVER(ORDER BY COL1PK, COL2PK) AS THIS_ROW,
    CAST(COL1PK AS VARCHAR(200)) || ';' || CAST(COL2PK AS VARCHAR(200)) AS GEN1
    FROM SCHEMA.TABLE
      ) AS T1
WHERE MOD(T1.THIS_ROW, [records_in_logpart]) = 0;

SQL SERVER:

SELECT T1.THIS_ROW, T1.GEN1
FROM (
    SELECT
    ROW_NUMBER() OVER(ORDER BY COL1PK, COL2PK) AS THIS_ROW,
    CONCAT(CAST(COL1PK AS VARCHAR(200)),';',CAST(COL2PK AS VARCHAR(200))) AS GEN1
    FROM SCHEMA.TABLE
      ) AS T1
WHERE THIS_ROW % [records_in_logpart] = 0;

Setting up ranges in Replicate

Once the query results are returned, tasks will need to be set up consistently in all the environments. Note that in non-Prod environments the data segments will be identical to the PROD one, hence if any testing needs to be done, values should be adjusted specifically to the environment the task is running in.

1. Open Qlik Replicate\QEM UI
2. Open the task where the table is registered in Designer view
3. Edit the selected table properties
4. Edit Parallel Load
5. Select “Use Data Range”

Qlik Replicate - Table Parallel Load Settings

6. Click “Select Segment Columns” and pick the columns you are going to segment the table by and click OK. By default, the PK columns will be automatically selected

Qlik Replicate - Table Parallel Load - Select Segmentation Columns

NOTE – for SAP application(DB) endpoints the MANDT field is implicitly taken from the endpoint CLIENT field and will not appear in the column selection criteria

7. Populate the segments with the ranges returned by the queries in ascending order and click “Validate”:

Qlik Replicate - Validating Data Segments settings

NOTE – “Validate” button only checks that all the input fields have been populated and that the data in those fields matches the field data type.

8. Correct any error that may be discovered and click “OK”.

NOTE – segments’ boundaries should be in an always-ascending order. Failure to comply may result in inconsistent data unload generating duplicate records and/or missing data.