How-to
Short answer: Create an integration with an Update an item action on the same process. Set the source table for the target table and map each column. Every row is copied.
Why it happens
There's no built-in way to copy rows between two child tables on a form. An integration can do it, because the Update an item action can fill a table from another table's rows.
How to fix it
- Create an integration with the trigger that fits your case.
- Add the Kissflow Process action Update an item on the same process.
- Set Table A (the source) as the source for Table B (the target).
- Map each Table B field to the matching Table A field. Don't map the row
_id. Every row is copied. - Test, then turn on the integration.
Updating rows directly with Update an item, rather than looping over them, also helps avoid concurrency issues. See the integration best practices.
If you want to combine two tables into one
- Add two Update an item actions, one for each source table.
- On the second action, use the filter to copy only unique values and skip duplicates.
Note
Avoid duplicating data across tables where you can. Prefer one data source, or add columns to the existing table.
