DB Update with multiple identification columns

[ThoCo]

Hello,
I have an issue with the DB Update node when using multiple identification columns.

The database is not updated as if there were no match with the table, even though there is a match (checked with Joiner).
Does anyone have any ideas how to solve this problem?

Thanks in advance

Thomas

[ScottF]

Hi @ThoCo and welcome to the forum.

When you say “the database is not updated” is it just that nothing happens, or an error is thrown, or…? Can you provide some additional detail from the log about warnings and/or errors?

An example workflow with some dummy data would be ideal, even if it only includes a local database (for example H2).

[ThoCo]

Hi ScottF,

There is no error but 0 rows are affected by the update.

I join the workflow and the Excel File. It’s a sql database, I have to check how I can provide that.
ePQR.xlsx (44.1 KB)

ePQR(2).knwf (15.3 KB)

[k10shetty1]

Hi @ThoCo,

Thanks for the update.

I’ve tried to replicate the issue using a test database. In my case, when the matching records are present in the database, the DB Update node works as expected and returns an update status of 1.

Could you share a few of the records from your database that are matching based on your Joiner query? That might help in identifying why the update isn’t going through, even though a match appears to exist.

Best,
Keerthan

[ThoCo]

Hi Keerthan,

After rechecking, I realized that I had chosen one of the two identification columns incorrectly. Now it works.

Thank you for your help and I apologize for the inconvenience.

Best,

Thomas