Pipelines - Delete unmatched records
I've been using pipelines to replace some synced tables that I need to be updated "live". Basically two nearly identical tables with the same primary key.
I've created a pipeline for when a recor...
Forum Discussion
Do you have some way of binding the two together that you can match between? Such as - when you create a record in Table B from Table A, are you logging the Record ID# in Table B so you can match them back and forth?
If you are - you could run a daily process that takes ALL the records in Table A and imports the current date into table B as a 'Date Last Seen from Table A', and then search for all the records in Table B that don't show as 'Today'. The assumption there is that if you don't update a value in Table B as having been seen today then it must have been deleted from Table A.
------------------------------
Chayce Duncan
------------------------------
I had a similar thought using a checkbox field called 'delete'. Basically the update process first sets all checkboxes to true, then the upsert process unchecks the boxes. After the upsert is committed, I delete all records where the checkbox is still checked. My concern there is an interruption in the process that results in all records being deleted.
I had hoped to do it within the pipeline not using new fields as I assume there is a method that my peabrain can't figure out.
------------------------------
Drew Voge
------------------------------