With the new inclusion of the Get Chart Image block in the Qlik Reporting connector in Qlik Application Automation, you now have more opportunities to notify a group of users with more in-depth data and charts using Slack or emails.

This article will guide you in sending your first chart image to Slack with an automation.

You can download an example of the automation from this article: Send-chart-image-slack.json

Full Automation

Instructions

1. Open the automation editor and search for the Qlik Cloud Services connector in the left-side menu.
   
   
2. Drag the blocks “Select Field Value” and “Create Bookmark” inside the canvas and fill in the required inputs.
   
   Mostly we will want to apply selections on one or more field values in the specified app and create a temporary bookmark using those values.
   
   
   
   
   
   

   Warning: Whenever the “Get Chart Image” block is to be used, we advise you to only use it with temporary bookmarks or pre-existing persistent bookmarks!

2. Search for the Qlik Reporting connector in the left-side menu, then drag the "Get Chart Image" block inside the editor and attach it below the previous block.
   
   Choose the same app you chose when creating the temporary bookmark and use the ID value received from the “Create Bookmark” block. 
   
   
   
   The height and width inputs are not required and if not filled in they will default to 1000.
   
   Manually insert the Object ID input; it can not yet be retrieved through an API call.
   
   To find the chart ID from the app, open the app, then click Edit Sheet, right-click the chart, and open the Share/Embed menu from the menu dropdown that appears. You will see the object ID of the chart under the chart preview section as shown below:
   
   
   

    

3. Add the 'Condition' block to check whether the "Get Chart Image" block has returned a successful response.
   
   
   
   
   1. If the condition block outcome evaluates to true:
      
      
      • Search for Slack connector from the left-side menu, add the "Upload File To Channel" block, and fill in all the required inputs.
        
        
        
        
      • The chart image gets posted on the Slack channel as shown below:
        
        
         

   2.  If the condition block outcome evaluates to false:

      • Add the "Update Run Title" block to specify that the "Get Chart Image" block failed due to an error.
        
        
        
        
      • Add an "Error" block to throw an error message from the "Get Chart Image" block and set the current automation run to be in a failed state.
        
        
        

The information in this article is provided as-is and will be used at your 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.

Environment

• Qlik Cloud 
• Qlik Application Automation 

When synchronizing Qlik Sense with Active Directory, you may encounter an error message saying "the User Directory Connector (UDC) is not configured, because the following error occurred: Setting up connection to LDAP root node failed. Check log file"

This often indicates a log on failure, i.e. the username and/or password is wrong.
 

Cause:

A common cause for this is wrong username and/or password.

Resolution:

1. Attempt to set up the UDC and receive the error message
2. Go to the the following location to get user management log file: %ProgramData%\Qlik\Sense\Log\Repository\Trace
3. Locate the QLIKSERVER_UserManagement_Repository_<Date/timestamp>.txt file and open it
4. Scroll to the bottom of the file
5. Read the content of the line marked by ERROR
6. If the error message is related to username and password related, move to the next steps, otherwise file a support case with us
7. Verify that the user and password actually exists, and that they are in the domain
8. In the username field, enter the domain name with a "back-slash", it should look like this domain_name\<username>
9. Enter the password normally.

The HubSection_Home resource filter in Qlik Sense refers to the button which allows a user to navigate back to the Hub from inside of an application.

Default ruleset:

Resolution:

If an administrator should want to disable this functionality for their users, for example, if the application is embedded into another page. Then they will want to disable the default rule named HubSections.

The result with this rule disabled is as follows for the end user:

The result of this change will disable this functionality for all users. If an administrator wants to provide this functionality to a select set of users then the administrator can create a new rule in this schema:

• Resource filter: HubSection_*
• Actions: Read
• Conditions: Some User Condition
  • Example: user.roles like "*Admin*"
    • This will show the Open Hub button for any user who has an Admin role assigned to their user account.
• Context: Both Hub and QMC

Using a Salesforce source endpoint, especially while using the Incremental Load source endpoint, all UPDATE operations are treated as INSERT operations for the table "UserRole". This leads to duplicate IDs found from the target table in the CDC processing stage.

Environment

• Qlik Replicate, all versions
• Salesforce source, all versions

Resolution

Set the task to UPSERT mode with Apply Conflicts set to Update the existing target record and Insert the missing target record. For more information see Apply Conflicts.

Note: this WA applied to Apply Change Mode, if the 'store changes' are enabled, duplicate ID is presented in __ct table still.

Cause

71 objects are missing the "CreatedDate" system field (including tables "AccountShare", "UserLogin", "UserRole", and similar). This is why Qlik Replicate can't identify if the change is inserted or updated, leading to both INSERT and UPDATE being converted to INSERT operation for these tables.

Internal Investigation ID(s)

00294581

A task containing tMysqlOutput component, which performs insert/update operations, has been blocked/suspended due to a PAGEIOLATCH_SH wait type status and has been pending for several hours.

Cause

Based on the SQL query check we figured out the avg_fragmentation_in_percent showing  90%+ , which means the index is maintenance badly. 

USE DBName;
GO
-- Find the average fragmentation percentage of all indexes
-- in the HumanResources.Employee table.
SELECT a.index_id, name, avg_fragmentation_in_percent
FROM sys.dm_db_index_physical_stats (DB_ID(N'DBName'),
OBJECT_ID(N'dbo.TableName'), NULL, NULL, NULL) AS a
JOIN sys.indexes AS b
ON a.object_id = b.object_id AND a.index_id = b.index_id;
GO

==Detecting Fragmentation==

The first step in deciding which defragmentation method to use is to analyze the index to determine the degree of fragmentation. By using the system function sys.dm_db_index_physical_stats, you can detect fragmentation in a specific index, all indexes on a table or indexed view, all indexes in a database, or all indexes in all databases. For partitioned indexes, sys.dm_db_index_physical_stats also provides fragmentation information for each partition.

The result set returned by the sys.dm_db_index_physical_stats function includes the following columns.

Resolution

Environment

• Talend Data Integration 7.3.1, 8.0.1

A task using ODBC as a target fails after an upgrade to 2023.5 or later versions:

Errors 00001888: 2024-09-09T10:31:56:332057 [TARGET_LOAD ]E: Failed (retcode -1) to execute statement: CREATE SCHEMA "CLILIBF" [1022502] (ar_odbc_stmt.c:5082) 

00001888: 2024-09-09T10:31:56:332057 [TARGET_LOAD ]E: RetCode: SQL_ERROR SqlState: 42000 NativeError: -552 Message: [IBM][System i Access ODBC Driver][DB2 for i5/OS]SQL0552 - Not authorized to CREATE DATABASE. [1022502] (ar_odbc_stmt.c:5090) 

Before the upgrade, the tasks may have encountered the same error but could be run using a Full Load.

Environment

• Qlik Replicate
• ODBC 
• DB2 iSERIES as target

Resolution

To resolve the issue, we will modify an Internal Parameter to the endpoints settings, as well as set a provider syntax.

1. Add the Internal Parameter:
   
   
   1. Go to the  Endpoint connection
      
      
   2. Switch to the Advanced tab
      
      
   3. Click Internal Parameters
      
      
   4. Modify the Parameter: additionalConnectionProperties 
      
      The old value should be DSN=TGT_PPCPROD
      If no parameter exists, create it.
      
      
   5. Add the new value: DSN=TGT_PPCPROD; DBQ=CLILIBF
      
      
      
      This tells the ODBC driver that any references to table names without an explicit schema name should be resolved in schema CLILIBF. 
      
      
2. Add the provider syntax
   
   
   1. Go to the  Endpoint connection
      
      
   2. Switch to the Advanced tab
      
      
   3. Locate Provider Syntax and add the value GenericWithoutSchema 
      
      
      
      This indicates to the endpoint to disregard schema information, which is the cause of the error.

Cause

Replicate Upgrade. Oracle to ODBC(iSeries) on 2023.5 will not do a Full Load. 

Internal Investigation ID(s)

QB-29117

Question I
What are the compatible operating systems?
The compatible operating systems can be found in the article: compatible-operating-systems.
Please check the section: Talend Remote Engine.

Question II
What are the compatible Java environments?
Java 8, Java 11, Java 17 can be used for task executions. By default, Talend Remote Engine uses Java 17 to run tasks. The compatible Java environments can be found in the article: launching-talend-cloud-remote-engine-for-aws-via-cloudformation.
Please check the section: Procedure ⇒ Step 10. 
Furthermore, there are no differences whether Talend Cloud Remote Engine for AWS is launched using Cloud Formation or AMI.

Question III
Where is the Remote Engine installed?
It is installed in the following directory.
/opt/talend/ipaas/remote-engine-client/

Question IV
Where can I find the settings file to make parameter changes?
The settings file is located in the following directory.
/opt/talend/ipaas/remote-engine-client/etc/

Question V
Where can I find further details on Talend Cloud Remote Engine for AWS?
Please refer to Qlik Talend Documentation: talend-cloud-remote-engine-for-aws.

Environment

Talend Cloud 

For general advice on how to troubleshoot Qlik Replicate latency issues, see Troubleshooting Qlik Replicate Latency and Performance Issues.

If your task shows latency issues, one of the first things to do is to set the logging component performance to trace and run the task you identified for five to 10 minutes and review the resulting task log.

We advise you to:

1. Open the task log in a text editor (such as Notepad++),
2. then search source latency 
3. and choose Find all in current document.

This will list all available latency information. We can now identify a trend. 

Remember, Target latency = Source latency + Handling latency.

No latency

[PERFORMANCE     ]T:  Source latency 0.00 seconds, Target latency 0.00 seconds, Handling latency 0.00 seconds (replicationtask.c:3703)

The source, target, and handling latency are all at 0 seconds.

Source latency

[PERFORMANCE     ]T:  Source latency 7634.89 seconds, Target latency 7634.89 seconds, Handling latency 0.00 seconds  (replicationtask.c:3793)

 [PERFORMANCE     ]T: Source latency 7663.00 seconds, Target latency 7663.00 seconds, Handling latency 0.00 seconds (replicationtask.c:3793)

[PERFORMANCE     ]T:  Source latency 7690.12 seconds, Target latency 7693.12 seconds, Handling latency 3.00 seconds  (replicationtask.c:3793)

[PERFORMANCE     ]T:  Source latency 7710.25 seconds, Target latency 7723.25 seconds, Handling latency 13.00 seconds  (replicationtask.c:3793)

The source latency is higher than the handling latency. The key point is to look at handling latency, it must be lower than the source latency.

Cause: 

• Source database busy
• Lack of network bandwidth to the source
• There are a lot of CDC changes to capture (the task has stopped for some time and only just resumed)
• There are a lot of CDC changes to capture (the source database has maintenance or a sudden influx of DML operations occurred)

If the source latency decreases during your monitoring, it is a good sign that the latency will recover; if it increases, review the causes mentioned above and resolve any outstanding source issues. You will want to consider reloading the task. 

Target latency

[PERFORMANCE     ]T:  Source latency 2.05 seconds, Target latency 7116.05 seconds, Handling latency 7114.00 seconds  (replicationtask.c:3793)

[PERFORMANCE     ]T:  Source latency 2.77 seconds, Target latency 7150.77 seconds, Handling latency 7148.00 seconds  (replicationtask.c:3793)

[PERFORMANCE     ]T:  Source latency 2.16 seconds, Target latency 7182.16 seconds, Handling latency 7180.00 seconds  (replicationtask.c:3793)

The target latency is higher than the source latency. 

Cause:

• Target is busy
• Lack of network bandwidth to the target 
• A bottleneck in the target database computing power, especially for cloud endpoints

If the target latency continues to increase, consider reloading the task. 

Handling latency

Identifying whether or not you are looking at handling latency or target latency can be tricky. When the task has target latency, the queue is blocked, so the handling latency will automatically be higher as well (remember: Target latency = Source latency + Handling latency).

The key point to decide if it is handling latency is to check if there are a lot of swap files saved in the sorter folder inside the task folder of the Qlik Replicate server. 

In addition, if the task log shows when the task is resumed, the handling latency increases dramatically from 0 seconds (or a low number) to a much higher value in a very short time. This can then be clearly identified as a handling latency:

2023-05-10T08:21:02:537595 [PERFORMANCE     ]T: Source latency 5.54 seconds, Target latency 5.54 seconds, Handling latency 0.00 seconds  (replicationtask.c:3788)

2023-05-10T08:21:32:610230 [PERFORMANCE     ]T: Source latency 4.61 seconds, Target latency 55363.61 seconds, Handling latency 55359.00 seconds (replicationtask.c:3788)

This log shows handling latency increased from 0 seconds to 55359 seconds after only 30 seconds of a task's runtime. This is because Qlik Replicate will read all the swap files into memory when the task is resumed. In this situation, you need to reload the task or resume the task from a timestamp or stream position.

Related Content

• Troubleshooting Qlik Replicate Latency and Performance Issues 

Environment

• Qlik Replicate

After a DB2 LUW upgrade from 11.1 to 11.5, Qlik Replicate tasks which read from the upgraded DB2 LUW Source Endpoint fail with the error:

[SOURCE_CAPTURE ]I: Error reading log buffer (db2luw_endpoint_proc.c:679)
[SOURCE_CAPTURE ]E: Error at 'Reading log records': Unexpected Error. Original SQLCODE -1263: ' message SQL1263N The archive log file "S0534570.LOG" is not a valid log file for
database "R3P" on database partition "0" and log stream "0".

Environment

• Qlik Replicate

Resolution

Perform a reload of the Qlik Replicate Task(s) and Table(s) which use the DB2 LUW Source Endpoint.

Cause

Upgrading a DB2 LUW environment changes the DB2 Transaction log format. 

References:
Start Event Viewer (Windows Server)
https://technet.microsoft.com/en-us/library/cc766401.aspx

What information appears in event logs? (Windows Server)
https://technet.microsoft.com/en-us/library/dd349798(v=ws.10).aspx

Open Event Viewer (Windows 7)
http://windows.microsoft.com/en-au/windows/open-event-viewer#1TC=windows-7

What information appears in event logs? (Windows 7)
http://windows.microsoft.com/en-au/windows/what-information-event-logs-event-viewer#1TC=windows-7

Qlik Replicate tasks using Oracle as a Source Endpoint fail after installing the Oracle July 2024 patch. 

All Qlik Replicate versions older than the 2024.5 SP03 release are affected.

Environment

• Qlik Replicate 2024.5 SP02 and below
• Oracle Source Endpoint with Oracle 2024 July patch (version 19.24)

Resolution

Upgrade to Qlik Replicate 2024.5 SP03 or later once available. 

In the meantime, Qlik has made early builds of 2023.5, 2023.11 and 2024.5 available. 

Download the early builds here: 

2023.5 SP07: https://files.qlik.com/url/qjfazk7fxftjmncu
password: cdesfgb8

2023.11 SP05: https://files.qlik.com/url/ndafzunah2srntqt
password: bl3xrefv

2024.5 SP03: https://files.qlik.com/url/fbfsznjidxt5nzra
password: cygie73l

Cause

The Oracle July 2024 patch introduced a change to redo events. Qlik has since provided a fix for Qlik Replicate which parses the redo log correctly. 

Internal Investigation ID(s)

RECOB-8698

Reference:

Oracle Database 19c Release Update July 2024 Known Issues

As a general reminder, all changes to the environment such as operating system patches, endpoint and driver patches, etc. should be tested in lower environments before promoting to production.

Using the qlik-cli it is possible to import a list of users to a tenant from a csv file.
It will be then possible to assign roles, entitlements and space permissions to the users before they log in to the tenant.


Here's a possible example of how to do that.

1.  Create a csv file called userlist.csv in this format (see attached sample file)
   
   

   Name,Email
   Mick Case,Mick.Case@example.com
   Davide Bironi,Davide.Bironi@example.com
   Kenny Handsley,Kenny.Handsley@example.com
   Leigh Kersriver,Leigh.Kersriver@example.com
   Gerry Vain,Gerry.Vain@example.com
   Tommy Ioni,Tommy.Ioni@example.com
   Terence Attendant,Terence.Attendant@example.com
   John Oughborne,John.Oughborne@example.com
   William Guard,William.Guard@example.com
   Renato Padovano,Renato.Padovano@example.com​

   
   
   
2. Save the following shell script and put it in the same folder as the csv file
   
   
   1. Powershell version (note: if the location of the qlik-cli is not added as an Environment Variable Path you will need to modify the script to include the full path in front of the command "qlik")  
      
      

      # Import the csv file as an array of objects
      $csv = Import-Csv -Path userlist.csv
      # Initialize a counter for the subject
      $counter = 1
      # Loop through each object in the array
      foreach ($row in $csv) {
          # Generate the subject using the counter
          $subject = "ExampleSubject" + $counter
          # Execute the qlik-cli command with the column values and the subject
          qlik user create --name $row.Name --email $row.Email --subject $subject
          # Increment the counter
          $counter++
      }​

       

   2. Bash version for UNIX systems:
      
      

      #!/bin/bash
      # Get the number of lines in the csv file
      lines=$(wc -l < userlist.csv)
      # Loop from the second line to the last line (skipping the header row)
      for ((i=2; i<=lines; i++))
      do
        # Get the name and email values from the ith line using cut
        name=$(cut -d, -f1 userlist.csv | sed -n "${i}p")
        email=$(cut -d, -f2 userlist.csv | sed -n "${i}p")
        # Generate the subject using the counter
        subject="ExampleSubject$counter"
        # Execute the qlik-cli command with the column values and the subject
        qlik user create --name "$name" --email "$email" --subject "$subject"
        # Increment the counter
        ((counter++))
      done​

3. Execute the scripts according to your operating system requirements
   
   

NOTE: users will be created with a temporary SubjectId like "ExampleSubject1", "ExampleSubject2", and so so on. After the first login, users will get a proper SubjectId. 
Roles, entitlements and space permissions will follow the users to the new subject.

Alternatives ways of adding users via scripts might be achieved via the an /api/v1/users CALL with the POST method and a payload like:

PAYLOAD:             
{
  "email": "name@example.com",
  "name": "First Lastname",
  "subject": "SubjectXYZ"
}

The information and the files in this article are provided as-is and will be used at your 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.

Environment

• Qlik Cloud 

Since QlikView 12.90 IR, the QlikView event log will no longer track license events (such as entitlement or CAL usage) when the log verbosity is set to medium.

Top track usage data set the verbosity to high.

Environment

• QlikView

Resolution

Previous versions tracked license events at the medium log level. The behavior in 12.90 IR was identified as a defect which is aimed to be resolved with 12.90 SR1.

Internal Investigation ID(s)

QV-25376

If a Qlik Sense document uses Section Access to restrict user access, the following error may be seen during data load:

Access was denied after reload. Check that the user that reloads the script is included in the section access part of the script.

Environment

• Qlik Sense Enterprise on Windows
• Qlik Cloud Analytics

Resolution

Multiple root causes and matching solutions exist: 

The user loading the script does not have ADMIN permission in Section Access

Verify that the user executing the script has ADMIN access in the Section Access table.

Field data is not upper-case

All field data (such as userID, email) must be written in upper-case.

Column name for Section Access (ACCESS, USER.EMAIL, USERID, etc) is wrong

Make sure the column names are correct. If these are not matched, use an "as" prefix to adjust it.

Example: ACCESS, USERID, USER.EMAIL

LOAD ACCESS, 
  EMAIL as USER.EMAIL, 
  REDUCTION, 
  OMITGROUP; 

SELECT ACCESS, 
  EMAIL, 
  REDUCTION, 
  OMITGROUP

Cause

• The user loading the script does not have ADMIN permission in Section Access
• Field data is not upper-case
• Column name for Section Access (ACCESS, USER.EMAIL, USERID, etc) is wrong

Related Content 

• Managing data security with Section Access (Qlik Sense on-premise)
• Managing data security with Section Access (Qlik Cloud Analytics)

When using Google Cloud BigQuery as the target endpoint, tables are created without a Primary Key (PK) by default, even if the source table has a PK defined. This behavior is by design. In this article, we demonstrate how to modify this behavior, allowing Qlik Replicate to create a Primary Key in the target table when the source table has a PK defined.

To change the behaviour, add the Internal Parameter $info.query_syntax.create_primary_key to the Google Cloud BigQuery target endpoint:

1. Go to the Google Cloud BigQuery Endpoint connection
2. Switch to the Advanced tab
3. Click Internal Parameters
4. Add the parameter: $info.query_syntax.create_primary_key
5. Add the value: ALTER TABLE ${QO}${TABLE_OWNER}${QC}.${QO}${TABLE_NAME}${QC} ADD PRIMARY KEY ( ${COLUMN_LIST} ) NOT ENFORCED
   
   For more information about Internal Parameter, see Qlik Replicate: How to set Internal Parameters and what are they for?
   
6. Save and re-run task

Environment

• Qlik Replicate all versions
• Google BigQuery all versions

When working with Google Cloud BigQuery as the target endpoint, the NUMERIC data type in the source database (e.g., IBM DB2 for iSeries) is mapped to the NUMERIC data type in Google Cloud BigQuery by default. Specifically, it defaults to NUMERIC(38,9), where the precision is 38 and the scale is 9. This allows for the exact representation of decimal fractions, making it suitable for financial calculations.

However, there are scenarios where optimizing data type mapping can help save storage space. This article is useful if you want to modify the default precision and scale. For example, instead of mapping the source NUMERIC(18,2) to the default NUMERIC(38,9) in Google Cloud BigQuery, you might prefer to map it directly to NUMERIC(18,2).

Additionally, the CHAR and VARCHAR data types in the source database map to STRING in BigQuery. By default, it maps to STRING, which implicitly means STRING(65535). This can be adjusted as needed to further optimize storage. In this sample, it maps to STRING($LENGTH). For example the CHAR(20) in source database maps to STRING(20) in GBQ.

Environment

• Qlik Replicate All versions
• Google BigQuery  All Versions

Detailed Steps

1. From the Qlik Replicate computer where you want to import the task, open the Qlik Replicate command line console by doing the following:

   From the Start menu, expand Qlik Replicate and then select Qlik Replicate Command Line. 

   A command-line console is displayed with the correct prompt for Qlik Replicate.
   
   Alternatively, open a Windows Command Prompt using As Adinistrator and change to "<product dir>\Attunity\Replicate\bin" (default location)
   
   

2. Run the following command:
   
   

   repctl.exe getprovidersyntax syntax_name=BigQuery >> BigQuery_2024_5_NumericStringLength.json

   
   If the DATA folder is a non-default location, add option -d data_directory in the command.
   
   
3. Edit the BigQuery_2024_5_NumericStringLength.json as outlined below, or download the example copy attached to this article: 
   
   
   1. Remove the first line and the latest line and include:
      
      

      command getprovidersyntax response:
      
      [getprovidersyntax command] Succeeded

   2. Modify the top few lines:
      
      Original:
      
      

      "provider_syntax": {
       "name": "BigQuery",
       "query_syntax": {

      Modified:
      
      

      "provider_syntax": {
      "name": "BigQueryNumeric", 
      "repository.provider_syntax": { 
      "name": "BigQueryNumeric",
      "query_syntax": {

   3. Original:
      
      

      "rep_type":    "kAR_DATA_TYPE_NUMERIC",
      "provider_data_type":    "NUMERIC",
      "has_precision_condition":    true,
      "from_precision":    1,
      "to_precision":    38,

      Modified:
      
      

      "rep_type":    "kAR_DATA_TYPE_NUMERIC",
      "provider_data_type":    "NUMERIC(${PRECISION},${SCALE})",
      "has_precision_condition":    true,
      "from_precision":    1,
      "to_precision":    38,

      Original:
      
      

      "rep_type":    "kAR_DATA_TYPE_STR",
      "provider_data_type":    "STRING"

      Modified:
      
      

      "rep_type":    "kAR_DATA_TYPE_STR",
      "provider_data_type":    "STRING(${LENGTH})",

4. Save changes and move the file to "C:\Program Files\Attunity\Replicate\data\imports", or your DATA folder.
   
   
5. Run the following command:
   
   

   repctl putobject data=BigQuery_2024_5_NumericStringLength

   Do not add the additional suffix ".json" in the end of the command as this will cause the command to fail.

6. Add the Internal Parameter syntax to the target endpoint:
   
   
   1. Go to the  Endpoint connection
   2. Switch to the Advanced tab
   3. Click Internal Parameters
   4. Add the parameter: syntax
      
   5. Add the value: BigQueryNumeric
      
      
      
      For more information about Internal Parameter, see Qlik Replicate: How to set Internal Parameters and what are they for?
      
      
7. Resume or Reload the task.

Related Content

• Backup Replicate DATA directory before you operate the repository
• Replicate - How to custom target endpoint syntax
• Replicate - How to create PRIMARY INDEX rather than PRIMARY KEY in Teradata Target DB

This article gives an overview of the available blocks in the Monday.com connector in Qlik Application Automation, as well as expand on basic example use-cases.

Monday.com is a powerful project management system — a complete Work OS designed to help your team complete projects efficiently, collaborate effectively, and grow online.  And Qlik Application Automation supports implementations involving Monday.com.

Content:

• Setting up Authentication
• Available Blocks
• Use Cases

Setting up Authentication

1. Login to your Monday.com account.
2. Click on your avatar icon at the top right corner, for a dropdown menu.
3. Under the newly appeared dropdown, head over to the ‘Developers’ tab.
   
   
   
   
4. Once in the Developer tab, head over to create a new app, or edit an existing app.
   
   
   
   During creation:
   • use the Redirect URL: ‘https://connector.qlikcloud.com/callback’
   • make sure we have at least these scopes enabled, for smooth functioning:  
     • boards:read
     • boards:write
     • workspaces:read
     • workspaces:write
     • users:read
     • users:write
     • account:read
     • notifications:write
     • updates:read
     • updates:write
     • tags:read
     • teams:read
     • assets:read

      

5. If you plan on using this app yourself, you can simply publish and generate the ‘client_id’ and ‘client_secret’ under ‘Basic Information’ section and connect in Qlik Application Automation with those values.
   
   
   
   
6. In case the user will be different from you, you can either add them into collaborators of your app, or share your app in the App Marketplace and setup installation for the other users.

Available Blocks

Assets

• List Assets     

Boards          

• List Boards    

Column         

• Create Column       
• List Columns
• Update Column Value       
• Update Simple Column Value     

Folders          

• Create Folder          
• Update Folder         
• Delete Folder
• List Folders   

Groups          

• Create Group          
• List Groups   
• Delete Group           

Items 

• List Subitems
• Create Item 
• Delete Item  
• List New And Updated Items Incrementally      
• Create Subitem      
• List Items      

Notifications 

• Create Notification 

Raw API         

• Do Generic Query   

Tags  

• List Tags        
• Create Or Get A Tag          

Teams           

• Delete Team From Workspace    
• Add Team To Workspace  
• List Teams    
• Add Teams To Board         

Updates        

• List Updates 
• Create Update        
• Delete Update         

Users 

• List Users       

Workspaces 

• List Workspaces      
• Delete Workspace  
• Add User To Workspace
• Create Workspace 

Use Cases

1. Sending notifications to Monday.com when a new deal is created in Hubspot.
   
   Set up the “List Deals Incrementally” block from Hubspot and drag the ‘Create Notification’ block from Monday.com, configure by selecting things like ‘User Id’ of the person to create notification, text that goes in the notification, project/post information of the notification etc.
   
   
   
   Similarly, we can also setup notifications when something occurs in Monday.com to send alerts on email/slack/teams using respective connectors on Qlik Application Automation.
   
   
2. Sync JIRA with Monday.com 
   
   When a new item is created in Monday.com, create a ticket in JIRA. And write back to Monday, that it has been updated to JIRA with issue ID.
   
   Also, if the ticket is already present, update the recent changes into JIRA.
   
   Below is an example flow depicting the same. We are also cross-storing IDs of JIRA and Monday into one another for easy access in updates.
   
   
   

   
   

Similar use-cases can be implemented with other ITSM tools like Service-Now etc.

The Qlik Sense log files can be easily collected using the Log Collector. 

The Log Collector is embedded in the Qlik Sense Management Console. It is the last item listed in the Configure Systems section.

For instructions on how to use the Log Collector, see Log collector (help.qlik.com).

Content

• Requirements
• Using the Log Collector
• What does the Qlik Sense Log Collector access?
• Manually collecting log files
• Older Qlik Sense Versions (3.1 and earlier)

Requirements

The user must be a root admin and have administrative permissions.

Using the Log Collector

The best way to gather these logs is to use the Qlik Sense Log Collector. If the tool is not included in your install, it can be downloaded from this article. 

1. Login to Windows Server on Qlik Sense node
2. Open Windows File Explorer
3. Navigate to Log Collector folder at C:\Program Files\Qlik\Sense\Tools\QlikSenseLogCollector
4. Press Shift key and right click on QlikSenseLogCollector.exe 
5. Select Run as different user
6. Enter Qlik Sense service account credentials.
7. Configure log collection
   • Date range to collect logs from (minimum of 5 days if possible)
   • Support case number to include in ZIP file name
   • Select options 
   • Include Archive logs
8. Click Collect
9. If Qlik Sense is not automatically accessible on the node, further options are presented.  
   • Qlik Sense is running and on this host
     this option to get more options on automatic log collection
   • Qlik Sense is not running or accessible
     this option allows to define the path to local Qlik Sense log folder
   • Qlik Sense is located elsewhere
     this option allows to enter FQDN of remote Qlik Sense server
10. Wait until collection is finished
11. Click Close
12. Open generated ZIP file in C:\Program Files\Qlik\Sense\Tools\QlikSenseLogCollector
    Note, no need to unzip the file, simple double click on the ZIP file to browse its content
    • Confirm it contains JSON and TXT files, if system info options were enabled in Step 6
    • Confirm there is one folder per node in the deployment, named in same way as the node
    • Confirm there is a Log folder representing Archived Logs from persistent storage
13. If ZIP content is incomplete, repeat steps above or contact support for further guidance
14. If ZIP content is accurate, attach ZIP file to support case for further analysis by Qlik

What does the Qlik Sense Log Collector access?

This list provides an overview of what system information the Qlik Sense Log collector accesses and collects.

• WhoAmI (information)

  C:\Windows\System32\whoami.exe

• Port status (information)

  C:\Windows\System32\netstat.exe -anob

• Process Info (information)

  C:\Windows\System32\tasklist.exe /v

• Firewall Info (information)

  C:\Windows\System32\netsh.exe advfirewall show allprofiles

• Network Info (information)

   C:\Windows\System32\ipconfig.exe /all

• IIS Status (iisreset /STATUS Display the status of all Internet services.)

   C:\Windows\System32\iisreset.exe /status

• Proxy Activated (information)

   C:\Windows\System32\reg.exe query "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings" | find /i "ProxyEnable"

• Proxy Server (information)

   C:\Windows\System32\reg.exe query "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings" | find /i "proxyserver" 

• Proxy AutoConfig (information)

   C:\Windows\System32\reg.exe query "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings" | find /i "AutoConfigURL" 

• Proxy Override (information)

   C:\Windows\System32\reg.exe query "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings" | find /i "ProxyOverride" 

• Internet Connection (information)

   C:\Windows\System32\ping.exe google.com

• Drive Mappings (information)

   C:\Windows\System32\net.exe use

• Drive Info (information)

   C:\Windows\System32\wbem\wmic.exe /OUTPUT:STDOUT logicaldisk get size

• Localgroup Administrators (information)

   C:\Windows\System32\net.exe localgroup "Administrators"

• Localgroup Sense Service Users (information)

   C:\Windows\System32\net.exe localgroup "Qlik Sense Service Users"

• Localgroup Performance Monitor Users (information)

   C:\Windows\System32\net.exe localgroup "Performance Monitor users"

• Localgroup Qv Administrators (information)

   C:\Windows\System32\net.exe localgroup "QlikView Administrators"

• Localgroup Qv Api (information)

   C:\Windows\System32\net.exe localgroup "QlikView Management API"

• System Information (information)

   C:\Windows\System32\systeminfo.exe

• Program List (information)

   C:\Windows\System32\wbem\wmic.exe /OUTPUT:STDOUT product get name

• Service List (information)

   C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -command "gwmi win32_service | select Started

• Group Policy (information)

  C:\Windows\System32\gpresult.exe /z

• Local Policies - User Rights Assignment (information)

   C:\Windows\System32\secedit.exe /export /areas USER_RIGHTS /cfg

• Local Policies - Security Options (information)

   C:\Windows\System32\secedit.exe /export /areas

• Certificate - Current User(Personal) (information)

   C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -command "Get-ChildItem -Recurse Cert:\currentuser\my | Format-list"

• Certificate - Current User(Trusted Root) (information)

   C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -command "Get-ChildItem -Recurse Cert:\currentuser\Root | Format-list"

• Certificate - Local Computer(Personal) (information)

   C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -command "Get-ChildItem -Recurse Cert:\localmachine\my | Format-list"

• Certificate - Local Computer(Trusted Root) (information)

   C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -command "Get-ChildItem -Recurse Cert:\localmachine\Root | Format-list"

• HotFixes (information)

  $FormatEnumerationLimit=-1;$Session = New-Object -ComObject Microsoft.Update.Session;$Searcher = $Session.CreateUpdateSearcher();$historyCount = $Searcher.GetTotalHistoryCount();$Searcher.QueryHistory(0, $historyCount) | Select-Object Title, Description, Date, @{name="Operation"; expression={switch($_.operation){1 {"Installation"}; 2 {"Uninstallation"}; 3 {"Other"}}}} | out-string -Width 1024

• UrlAclList (information)

   C:\Windows\System32\netsh.exe http show urlacl

• PortCertList (information)

   C:\Windows\System32\netsh.exe http show sslcert

Manually collecting log files

Any versions of Qlik Sense Enterprise on Windows prior to May 2021, do not include the Log Collector.

If the Qlik Sense Log collector does not work then you can manually gather the logs.

• Default storage (before archiving): C:\ProgramData\Qlik\Sense\Log
• Default archive storage: C:\ProgramData\Qlik\Sense\Repository\Archived Logs
• Manual retrieval of Reload logs: How to find the Script (Reload) logs in Qlik Sense Enterprise

For information on when logs are archived, see How logging works in Qlik Sense Enterprise on Windows.

Older Qlik Sense Versions (3.1 and earlier)

Persistence Mechanism Current Logs(Active Logs) Archived Logs

Note: Depending on how long the system has been running, this folder can be very large so you will want to include only logs from the time frame relevant to your particular issue; preferably a day before the issue began occurring.

Related Content

How logging works in Qlik Sense Enterprise on Windows 

Qlik NPrinting SLK License cannot be applied or updated after the upgrade.

Licensing fails with:

The Licence Service is not responding. Restart the Qlik NPrinting License service

The Qlik NPrinting log files read:

"errorMessage":"Post \"https://license.qlikcloud.com/v1/definitions/signed\": dial tcp: lookup license.qlikcloud.com: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.","errorType":"LICENSES-InternalServerError","level":"info","logTraceId":"bf71fd0bcf272dd3528824ac4fb5f3a6","statusCode":500

"error":"Post \"https://license.qlikcloud.com/v1/definitions/signed\": context canceled","level":"error","logTraceId":"d7c48ffd76242e3522db613652462ee5","message":"Failed to fetch license definition."

"errorMessage":"Too much time has passed since the last license update","errorType":"LICENSES-OutdatedLicense","level":"info","logTraceId":"e7c3a2cc454f5dc843b68e5bb5e6840c","statusCode":403

Resolution

This issue is being caused by the license server being unreachable. If the server has internet connectivity, then the likely root cause is a proxy being deployed.

Follow these steps to troubleshoot and resolve the issue:

1. Login to Qlik NPrinting Server with  Service Account and open Qlik NPrinting Web Console with NPrinting Service Account.
   
   
2. Verify that the Qlik NPrinting License service is up and running.
   
   
3. Try to restart the Qlik NPrinting License service and try to apply for the Qlik NPrinting SLK License before going to the next step.
   
   
4. Verify that the Qlik NPrinting server has an active internet connection and that connectivity to license.qlikcloud.com on port 443 is possible from the server running the Qlik NPrinting licensing service.  (You must get "default backend - 404" in the browser when accessed to license.qlikcloud.com)
   
   
5. In some rare cases, the Server only has temporary access to the Internet, so sometimes it is able to connect to https://license.qlikcloud.com and sometimes not. It needs to have permanent access to the licence-URL, to be able to correctly work.
   
   If you are in the above rare cases or if the sync doesn't seem to be performed, there is a way to force the sync: remove one/more characters from the SLK License and click to "apply".
   
   The license will be refused as it's an incorrect one. This action will force the license synchronization. Now, try to apply with an actual SLK License.
   
   
6. If the above did not resolve the issue, check if you have a proxy configured in the NPrinting Server.
   
   
   1. Open Internet Options from Control Panel and check for Proxy IP/URL
      
      
      
      
   2. If the Proxy is configured, do the changes accordingly in %Program Files%\NPrintingServer\NPrinting\License\license.configusing Licensing service proxy Setup 
      
      
   3. Make sure to Stop and Start the Qlik NPrinting licensing service before and after performing the changes.

Cause

When you upgrade the Qlik Nprinting Server, the existing configurations files will be overwritten to default configurations files, and any changes done before the upgrade have to be updated again.

So make sure to take a backup of the Files (Eg: Config) and Folders before performing the upgrade.

Environment

Qlik NPrinting 

Related Content

Licensing service proxy authentication 
Licensing Qlik NPrinting offline 

Oracle-to-Oracle bidirectional tasks fail after an upgrade to Qlik Replicate 2024.05.

The tasks crash without an error or start failing with a duplicate constraint error on the attrep_loopback_prevention table.

This issue may also impact bidirectional tasks with other endpoints.

Resolution

No fix or workaround is currently available. Qlik is diligently working on a solution and will provide a timeline for a patch by the end of September 2024.

Internal Investigation ID(s)

QB-29163

Environment

• Qlik Replicate v2024.05