topic Re: Data discrepancy with Hard delete flag transformation(All non PK key have NULL in landing table) in Qlik Replicate

Data discrepancy with Hard delete flag transformation(All non PK key have NULL in landing table)

Kohila — Thu, 03 Aug 2023 01:34:02 GMT

We have active replication task running on the version 2022.5.0.815, with source as SAPS4 Application end point(trigger based) to target Azure Synapse analytics with both apply changes and Store changes enabled. Replication using LS and LR task and no log stream task for couple of tables.

We have comprises the hard delete logic and upsert for LR task which is taking Delete event as update and making all the non primary key values to Null in both target CT table(store change) and base landing tables as well. But here the expectation is that the NULL should be updated for only CT non primary key values and landing table entry should be updated with deleted flag and datetime having other non key values as it is before delete event.

We clearly see this is happening in this version 2022.5.0.815 and not in 2021.11.0.554. when delete happens in version 2021.11.0.554, it behaves as expected mentioned above. Is it any bug reported for this version? Is anyone using this version and your landing table had issue and any workaround suggested by Qlik.

Re: Data discrepancy with Hard delete flag transformation(All non PK key have NULL in landing table)

OritA — Thu, 03 Aug 2023 07:55:02 GMT

Hi,

Please open a salesforce case for this issue and attach to the case the task diagnostic package and the exact description of the expected result so we can review the task setting and better understand the issue.

Thanks & regards,

Orit

Re: Data discrepancy with Hard delete flag transformation(All non PK key have NULL in landing table)

Heinvandenheuvel — Fri, 04 Aug 2023 21:55:59 GMT

I suspect this question is too complex for a community forum to be expected to be of help.

As you submit your issue to support as a case, you may want to first try the latest release - 2023.5.0.152

Having said that, assuming I read your somewhat cryptic (LS? LR? ) message correctly, it seems to me that the the 2022 version is correct. The "U" line in the the CT table should be the same as the one in the base table on target, unless some DB level triggers changes that behind the back of Replicate.

If you need the CT table to be different from the Base, you'll needs two distinct task feeding of the same logstream.

Hein.

Re: Data discrepancy with Hard delete flag transformation(All non PK key have NULL in landing table)

Michael_Litz — Fri, 04 Aug 2023 22:43:30 GMT

Hi @Kohila ,

Thank you for opening a sales force case for this. I have replied into the case with the steps for migration from and between the 2021 and 2022 versions of replicate. I will be updating this community post with those steps after we resolve the issue in your environment.

Thanks,
Michael Litz