Hi

I am trying to calculate the month to date sales for last month. I am using an auto calendar.

here is my Formula

Sum({<[TXDATE.autoCalendar.MonthsAgo]={1}, TCODE={'IN'}, [TXDATE.autoCalendar.Month] ={"<=$(=Num(Month(Today()))) "} >} AMOUNT)
-
Sum({<[TXDATE.autoCalendar.MonthsAgo]={1}, TCODE={'CN'}, [TXDATE.autoCalendar.Month] ={"<=$(=Num(Month(Today()))) "} >} AMOUNT) 

Hi,

We have a replication task with Postgresql v17 as target endpoint working without issues for few days.
However, since this weekend, the task is looping on the same "timout" issue (Target table contains billions of rows):

00011719: 2026-10-03T05:42:34 [SORTER          ]I:  Task is running  (sorter.c:714)
00011718: 2026-10-03T05:50:23 [TARGET_APPLY    ]I:  Error in bulk, bulk state: bulk confirmed record id - '476716', bulk last record id - '404495777', confirmed record id - '396263857', sorter confirmed record id - '396263857'  (bulk_apply.c:2511)
00011718: 2026-10-03T05:50:23 [TARGET_APPLY    ]I:  Failed (retcode -1) to execute statement: 'UPDATE <...>' [1022502]  (ar_odbc_stmt.c:2852)
00011718: 2026-10-03T05:50:23 [TARGET_APPLY    ]I:  RetCode: SQL_ERROR  SqlState: 57014 NativeError: 1 Message: ERROR: canceling statement due to statement timeout;
Error while executing the query [1022502]  (ar_odbc_stmt.c:2858)
00011718: 2026-10-03T05:50:23 [TARGET_APPLY    ]I:  Failed to execute update statement.

The timeout seems to happen on the Database side every 25 minutes:

026-10-03 06:46:30 CEST **** user=****, db=****, client=****, appli=QlikReplicate/2025.11 (postgresql), sessionid=**** ERROR:  canceling statement due to statement timeout
[...]
2026-10-03 05:50:23 CEST **** user=****, db=****, client=****, appli=QlikReplicate/2025.11 (postgresql), sessionid=**** ERROR: canceling statement due to statement timeout

We have tried to change this timeout on client side (Qlik connection) with below "Internal Parameters" set on the target endpoint:

• afterConnectScript => set statement_timeout=<0 et 86400000>
• executeTimeout => <0 et 86400>

But also on the role (user) used to connect with the database:

ALTER ROLE d9dext SET statement_timeout = <0 et 86400000>;
SELECT * FROM pg_db_role_setting;

Both didn't have any effect, the timeout still occuring every 25 minutes...

Any clues on what is happening? Seems to be the driver used by Qlik which is overriding the "statement_timeout" property...

I have an expression which is given below:

(Sum({<Year={$(=Max(Year))},Company={"ITC"},DTNo={$(=Min(DTNo))} >}Contr)

/

Sum({<Year={$(=Max(Year))},Company={"ITC"},DTNo={$(=Min(DTNo))} >}Volume))
/1000

Please let me know is InputSum works here because in a single expression InputSum is working but in that type of calculation logic it's not working.

Hi,

We are hitting an issue where table names containing non-ASCII characters (Norwegian Ø) fail against a Databricks Lakehouse (Delta) target. The character survives DDL generation but is corrupted in the metadata lookup, so Replicate cannot find the table it just created.

Qlik Replicate: 2026.5.0.169, Windows
Source: IBM DB2 for LUW via Log Stream
Target endpoint: Databricks Lakehouse (Delta), Unity Catalog enabled, staging type Databricks Volume
Databricks ODBC driver: 2.10.0.1002 (64-bit)

DETAILS:

CREATE TABLE sends the correct UTF-8 name:
CREATE TABLE `[REDACTED]`.`transportør` ( `transportør` DECIMAL(6,0) NOT NULL, ... ) USING DELTA

DESCRIBE TABLE sends a corrupted name:
09:12:34 Failed to DESCRIBE TABLE
SqlState: 42P01 NativeError: 80
[TABLE_OR_VIEW_NOT_FOUND] The table or view `[REDACTED]`.`transport?r` cannot be found.
Failed to get table transport?r definition
Table '[REDACTED]'.'transport?r' does not exist, insufficient privileges or no supported columns

Because the lookup fails, Replicate treats the table as new, skips the drop, and issues CREATE, which then fails:
SqlState: 42P07 NativeError: 35
[TABLE_OR_VIEW_ALREADY_EXISTS] Cannot create table or view `[REDACTED]`.`transportør` because it already exists.

The table is suspended and never loads. Tables without Ø in the name work normally in the same task.

VERIFIED
- The character is a normal U+00F8. Verified in Databricks: hex(column_name) returns C3B8, identical in both schemas.
- Column names with æ/ø/å work fine. For example, `transportør` are created and populated correctly as columns.
- The Replicate user has full privileges on the schema. Manual DROP TABLE from the Databricks SQL editor succeeds.
- The target tables were dropped manually before retrying, so TABLE_OR_VIEW_ALREADY_EXISTS is not caused by leftover objects.

ALREADY TESTED, NO EFFECT
1. Global rule RENAME_TABLE with expression:
replace(replace(replace(lower($AR_M_SOURCE_TABLE_NAME),'Æ','æ'),'Ø','ø'),'Å','å')
This produces the correct lowercase name in CREATE TABLE, but DESCRIBE TABLE still sends transport?r.
2. Server setting "Support special characters in column names used in expressions".
3. Databricks ODBC DSN option "Unicode SQL character types" (UseUnicodeSqlCharacterTypes), with a restart of the Replicate service.

QUESTIONS
1. Is there an internal parameter on the Databricks Lakehouse (Delta) endpoint that controls character encoding for identifiers in metadata queries, so non-ASCII table names survive the DESCRIBE TABLE lookup?
2. If not, can you confirm this is the documented ASCII limitation for the Databricks target, and whether support for non-ASCII table names is on the roadmap?
3. Is the inconsistency itself considered a defect? The same task encodes the same table name correctly in DDL and incorrectly in metadata lookups.

We are applying an ASCII transliteration of the table names as a workaround so the tables load, but we would prefer to keep the original names.

Data can help online retailers understand what customers are actually looking for. By analyzing searches, product views, purchases, and seasonal demand, fashion businesses can improve the way they organize and present their collections.

For example, shoppers searching for formal dresses for women may respond differently to products based on occasion, color, fabric, or price range. Understanding these patterns can help online fashion stores create more useful shopping experiences. Brands such as Sablev Vogue can use customer insights to make their collections easier to discover and more relevant to different shopping occasions.

I saw this post yesterday and asked the following question in that thread but no one saw it...

Can anyone tell me where I might find more of these expression values? For instance;

'<S1>' = Solid Line

'<S2>' = Dashed Line

'<S3>' = Etc....

What about line widths..? '<W1>' ? What other options are there? '<R1>'? '<T5>'? '<D3>'? '<K2>'? Anything else....? A comprehensive list would be great!

Thank you.

Accepting a job offer is an exciting milestone, but knowing how to respond professionally can feel overwhelming. Once you get that official email or phone call, taking the right steps ensures a smooth transition into your new role. Here is a clear guide on how to accept the job (รับงาน) offer with confidence, along with easy-to-use templates and essential etiquette rules.

Step 1: Review the Offer Carefully

Before you send your formal acceptance, double-check all the details in your written offer letter:

• Salary and Benefits: Confirm the compensation matches what you discussed.

• Start Date and Hours: Ensure the timeline gives you enough time to give notice at your current job.

• Job Title and Responsibilities: Make sure the core duties align with the job description.

If any detail seems unclear, ask for clarification before you officially accept.

I wanted to share a technical white paper I published that documents
a novel solution to a CDC serialization challenge in Qlik Replicate
during mainframe-to-cloud migration.

THE PROBLEM:
STCK-based binary surrogate keys in mainframe MIS systems cause CDC
serialization failures in Qlik Replicate when migrating to AWS Aurora
PostgreSQL. The binary format breaks change event ordering and
traceability during active migration.

THE SOLUTION — Binary Key Bridging Pattern:
A dual-key architecture that preserves the original STCK binary key
while generating a UUID surrogate key for cloud-native compatibility.
This enables reliable CDC without data loss or event ordering failures
during zero-downtime migration.

This pattern is part of a broader 5-layer Live Data Coexistence
Framework (LDCF) that enables enterprise MIS modernization without
system downtime.

Published Paper:
Zenodo: https://zenodo.org/records/21313169
LinkedIn Post: https://lnkd.in/p/gaA4tN3n

Has anyone else encountered STCK binary key issues with Qlik Replicate
on mainframe sources? Would welcome feedback from the Qlik engineering
or product team.

Krishan Kumar