Hi,

We have upgraded Qliksense to the latest May 2026 version, and it seems the multi-KPI visualization has been deprecated and Qliksense recommends using the natively supported custom styles option for sheet styling. I've tried to migrate CSS code from multi-KPI to sheet styling, but running into a problem that only half of the CSS code can be copied into the styles text editor. Is this intended? If so, why is there such a limitation on how many characters or lines of code we can use? Can someone explain? 

Below is the Talend on premise version installed on my machine.

Talend Data Management Platform

Version: 8

Build id: 20250218_0945-patch

License Expiration date: 05/24/2027

In this Talend Version I am not able to see the tSalesforce Related components. I am unable to download it from website. Could you please assist me how to get/install the tSalesforce Related components?

Thanks in advance for your help!

As a licensed Qlik Sense Enterprise customer evaluating a QlikView modernization project, is there a self-service evaluation tenant or migration tenant available so that we can execute QV2QS ourselves?

https://community.qlik.com/t5/Integration-Extension-APIs/QlikView-to-Qlik-Sense-Converter-Tool/td-p/2548038?utm_source=chatgpt.com

Hi,

I am working with Qlik SaaS load script and I have a question about the reload log behavior during a LEFT JOIN.

I have a script that creates an invoice-agreement bridge table using IntervalMatch. The result is correct, and in the Data Model Viewer I do not see any duplicated table. However, during reload, the log shows a table name with a -2 suffix when joining the fact data into the interval match result.

Relevant code:

TempInvoiceAgreementMatch:
INTERVALMATCH (InvoiceDateNum, Customer)
LOAD DISTINCT
    ValidFromNum,
    ValidToNum,
    Customer
RESIDENT TempAgreementsForMatch;

LEFT JOIN (TempInvoiceAgreementMatch)
LOAD DISTINCT
    ValidFromNum,
    ValidToNum,
    Customer,
    AgreementNumber,
    AgreementFixedAmount
RESIDENT TempAgreementsForMatch;

DROP TABLE TempAgreementsForMatch;

LEFT JOIN (TempInvoiceAgreementMatch)
LOAD DISTINCT
    InvoiceDateNum,
    Customer,
    [Doc_VBELN],
    InvoiceMonthNum
RESIDENT TempFactForMatch;

DROP TABLE TempFactForMatch;

The reload log shows something like this:

TempInvoiceAgreementMatch << TempAgreementsForMatch
Lines fetched: 420,516

TempInvoiceAgreementMatch-2 << TempFactForMatch
Lines fetched: 4,632,847

MapFirstAgreementMonth << TempInvoiceAgreementMatch
Lines fetched: 943

AllocationBase_Temp1 << TempInvoiceAgreementMatch
Lines fetched: 1,344

InvoiceAgreementBridge << TempInvoiceAgreementMatch
Lines fetched: 107,713

The final result is correct, and TempInvoiceAgreementMatch-2 does not appear in the final data model.

My question:

Is TempInvoiceAgreementMatch-2 in the reload log just an internal temporary/staging table name that Qlik creates while processing the LEFT JOIN, or does it indicate that Qlik is actually creating a separate table during the join?

Thanks.

Qlik has a Sankey.
We built one for the flows that outgrow it.

Released a new Sankey Chart extension for Qlik Sense, designed to visualize multi-stage flows when the native chart runs out of room.

Useful for analyzing how value moves through stages — budget allocation, supply chains, customer journeys, energy flows, website traffic, conversion funnels.

Where Qlik's native Sankey caps at 5 dimensions, ours goes to 10.
Where the native selects only the source end on flow click, ours selects both at once.

Plus gradient links, level headers, layout sliders, detailed tooltips, and more.

➡️‌ Full announcement on our blog
Demo app and free trial available.

Happy to answer your questions.

Hi, we've recently had to enable a HTTPS proxy on our qlik machine, done via the HTTPS_PROXY environmental proxy.

To attempt to control which data doesn't go through the proxy we are utilising NO_PROXY.

Our Kafka endpoint, with the schema registry end point as remained unchanged through out this.

We have however added the schema registry hostname, as well as it's IP, to the NO_PROXY environmental variable.

We have added the environmental variables to the site_arep_login.sh (we only run a single instance) as advised: 

cho "export NO_PROXY=gds,.gds,amazonaws.com,gds-confluent-schema-registry.gds" >>$QLIK_REPLICATE_BASE_DIR/bin/site_arep_login.sh \
    && echo "export no_proxy=gds,.gds,amazonaws.com,gds-confluent-schema-registry.gds" >>$QLIK_REPLICATE_BASE_DIR/bin/site_arep_login.sh \
    && echo "export HTTP_PROXY=\$HTTP_PROXY" >>$QLIK_REPLICATE_BASE_DIR/bin/site_arep_login.sh \
    && echo "export http_proxy=\$HTTP_PROXY" >>$QLIK_REPLICATE_BASE_DIR/bin/site_arep_login.sh \
    && echo "export HTTPS_PROXY=\$HTTPS_PROXY" >>$QLIK_REPLICATE_BASE_DIR/bin/site_arep_login.sh \
    && echo "export https_proxy=\$HTTPS_PROXY" >>$QLIK_REPLICATE_BASE_DIR/bin/site_arep_login.sh \

 And I have confirmed that the pid Qlik is running under has the values.

However, when we start the task it fails with a curl 56 / HTTP code 403, suggesting the data is still going through the proxy.

The COMMUNICATION channel logs also appear to show that NO_PROXY is not picking up our environmental variable, and appears to be hard coded:

00000617: 2026-06-05T11:57:16:761902 [COMMUNICATION   ]V:  CURL DEBUG (TEXT): Uses proxy env variable no_proxy == 'localhost,127.0.0.1'  (at_curl.c:775) 

00000617: 2026-06-05T11:57:16:762203 [COMMUNICATION   ]V:  CURL DEBUG (TEXT): Uses proxy env variable https_proxy == 'http://gblprx.landg.com:80'  (at_curl.c:775)

I've even entirely removed any proxy environmental variables, so no proxy is set anywhere and I still get the line about using proxy env no_proxy with the same values, even though it's not set on the system.

Wondered if anyone else has experienced the same and has a solution? I've tried 2023.11, 2025.11, and 2026.5 - in all of these I've tried setting the proxy inside the qlik app at the server level instead, leaving the environmental variables empty, and then leaving 'use Proxy' unchecked for the Kafka schema registry - but it still ends up picking up the server settings and saying it's using no_proxy with localhost,127.0.0.1

Qlik didn't have it.
We built it for Qlik.

Just released the Circular Dendrogram extension for Qlik Sense, a new way to visualize hierarchical data as a radial tree.

It is useful when you need to see how a hierarchy is structured, not just compare values or levels. Think org charts, product taxonomies, account hierarchies, cost centers, file structures, scientific classifications, and other nested data.

Unlike a treemap, it doesn't pack hierarchy by value.
Unlike a sunburst, it doesn't stack levels in rings.

Instead, every parent-child relationship is drawn as an edge, with branches fanning out from the center to the leaves. Click a leaf, and the full chain back to the root lights up.

➡️ Full announcement on our blog
Demo app and free trial available.

I have a Qlik Sense table where the dimension is limited using:

Dimension → Limitation → Show first N rows

The table correctly displays only those N rows.

However, the Totals row still calculates using all rows, not just the limited/displayed rows.

My requirement is:

• Show only first N rows in the table

• Totals row should reflect only those same N rows

• Total mode must remain = Auto because the measure contains complex calculations

Example:

If I limit the dimension to Top 3 rows, the table shows:

A, B, C

But the Totals row still calculates using all rows (A+B+C+D+E) instead of A+B+C.

Is there a way to make Auto totals respect the dimension limitation, or is this expected Qlik behavior?

I would like to avoid switching Total mode to Sum, since the measure relies on Auto total logic.