Skip to main content
Announcements
Introducing Qlik Answers: A plug-and-play, Generative AI powered RAG solution. READ ALL ABOUT IT!
cancel
Showing results for 
Search instead for 
Did you mean: 
Ole_Dufour
Contributor III
Contributor III

Insertion of multiple lines

In our source database we have a household table.
A household can have multiple adresses.
A household has one more or persons.
A person can have 2 statuses, 'active' and 'inactive'.
Once a person becomes 'active' we want all of his household's adresses inserted in the destination database.
However, our current observation indicates that only one address is being inserted.

The question that arises is whether it is possible for a Change Data Capture process to insert multiple rows.
I am aware that it is possible to update multiple rows by setting the 'updateOneRow' parameter to false. (see below)
Is there an equivalent option for inserts?

Ole_Dufour_0-1700130503184.png

 




Labels (1)
1 Solution

Accepted Solutions
Heinvandenheuvel
Specialist III
Specialist III

Not going to happen. Replicate is strictly one-on-one-or-none

You should have " household's adresses inserted in the destination database." already. Period.

I supposed  you could delete the addresses on source (with  ignore errors) and re-insert, or (safer), make an update (insert if does not exist flag) to each and every one of them. it could even be a x=x non-update, but I'd advise a bonus field with the active flag perhaps or (more meaningful) he last activation date.

Hein.

View solution in original post

3 Replies
warne59
Contributor
Contributor

In an adjacent blank column starting at the level of your data (say D2) type 1 -> D3 type 2. Select D2 and D3 and at the bottom right corner of the cell double click. This should run the numbers down to number 33. Copy this list and paste 1 cell below 33. Select all your data and the 2nd 1 to 33 -> and Data -> Sort, Lowest to highest. Now Delete column D figures.

Heinvandenheuvel
Specialist III
Specialist III

Not going to happen. Replicate is strictly one-on-one-or-none

You should have " household's adresses inserted in the destination database." already. Period.

I supposed  you could delete the addresses on source (with  ignore errors) and re-insert, or (safer), make an update (insert if does not exist flag) to each and every one of them. it could even be a x=x non-update, but I'd advise a bonus field with the active flag perhaps or (more meaningful) he last activation date.

Hein.

Ole_Dufour
Contributor III
Contributor III
Author

Hi Hein,

Ok. Touching the source database is a no go however. 

Thank you,

Ole