Refering to case 00035495 which is closed to early.

[J-J]

Can you please reopen case 00035495 ? Thanks.

Point 1.
An update is an update is an update.
Qlik should not care if columnn values are changed or not.
This is a basic CDC principle. Unchanged row updates can be valuable.
CDC tooling including our predecessors supports this by default.

Point 2.
In 2018 we agreed with Attunity on a workaround based on a Global Transformation and the $AR_H_COMMIT_TIMESTAMP.
We see this as a gentlements agreement. Qlik compromised this agreement.
So we urge again to fix this!

Point 3.
At de Volksbank we are dissappointed in the way Qlik handles the bug and our complaints.

[Heinvandenheuvel · Accepted solution]

This topic is inappropriate, and not useful as provided, for a general, public, and commitment free discussion.

I recommend you delete this topic and escalate through Qlik support first, and if that does not give a satisfactory result escalate though your Qlik Sales contact.

The individual point 1 and 2 may well, individually please, be worthy of a general discussion to  warn others about potential disappointing choices and perhaps workarounds. If you go that route, please be sure to include as much details as possible for the topics to be usable by random readers and folks trying to help.

Groetjes,

Hein