filter logic for export API

[Aworwui]

Dear All,
I configured the API Sync module and will kindly asked if I can filter the exported record through the export API module

Regards
Archie

[mmcev106]

We attempted to add this feature a year ago, but ran into some compatibility issues with incremental exports that we would need a larger support budget in order to resolve. It is a lot more complicated than the import "Filter Logic" feature, which only supports full syncs every time. Here are some notes I left in the code in case you're curious:

If ever try to add filter logic here again in the future,
remember a simple export filter logic feature is incompatible with incremental change detection.
During the periods when a record does not match filter logic, incremental changes for that record are ignored permanently
(regardless of whether the record matches the filter logic again in the future).
To work around this, we may need to store the last sync time of each individual record and use it to "catch up"
with past changes if/when unmatched records begin matching again (likely via a full sync of just those records).

[Aworwui]

Dear Mark, Thanks very much for the information I will take a shot at it and update you about my try Regards Archie From: Mark McEver ***@***.***> Date: Monday, 29 August 2022 at 3:24 PM To: vanderbilt-redcap/api-sync-module ***@***.***> Cc: Archibald Kwame Worwui ***@***.***>, Author ***@***.***> Subject: Re: [vanderbilt-redcap/api-sync-module] filter logic for export API (Issue #16) *** This message originated outside MRCG @ LSHTM *** We attempted to add this feature a year ago, but ran into some compatibility issues with incremental exports that we would need a larger support budget in order to resolve. It is a lot more complicated than the import "Filter Logic" feature, which only supports full syncs every time. Here are some notes I left in the code in case you're curious: If ever try to add filter logic here again in the future, remember a simple export filter logic feature is incompatible with incremental change detection. During the periods when a record does not match filter logic, incremental changes for that record are ignored permanently (regardless of whether the record matches the filter logic again in the future). To work around this, we may need to store the last sync time of each individual record and use it to "catch up" with past changes if/when unmatched records begin matching again (likely via a full sync of just those records). — Reply to this email directly, view it on GitHub<#16 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ALEGBIRXYEHRRDA2QJOVOYLV3TI3TANCNFSM57UQSXXA>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[govindsoniox]

@Aworwui I believe this would be real good addition to filter at source. I have been in touch with VUMC team again this month and heard it is still the case for this module. I believe some other applications which use the log table to sync , they could filter on this if I am not wrong ( For example I got to see the code of PHP plugin of OpenSpecimen which does achieve this... How did you manage your needs then?