getIncrementalUpdates and TeamRaiserGift record timestamp

Szymon Zaleski
Szymon Zaleski
Seventh Anniversary Kudos 1 Name Dropper Participant
in Blackbaud Luminate Online® & Blackbaud TeamRaiser® Discussions

We are using LO Web Services to build a local data warehouse storing LO data used for reporting. I've recently run into a problem, where a constituent record (X) of a Team Raiser participant was determined to be a duplicate and merged into another record (Y). However, the duplicate record X, prior to the merge, had gifts donated to their Team Raiser.

During the merge the ParticipantConsId field on the Team Raiser Gift record was updated to Y, but the LastModify timestamp on the Team Raiser Gift remained unchanged. Our daily sync updated the constituent X record to removed, but it did not update the Team Raiser Gift record with the new ParticipantConsId (Y) causing a discrepancy in the data. When I run getIncrementalUpdates on the Team Raiser Gift or query by ModifyDate for the time when the constituent was merged, it does not return the gift in question. I had to run getIncrementalInserts for when the gift was originally created to actually pull that gift into the sync and update it in the data warehouse.

I believe this to be an error on the Blackbaud side, as this gift should have its LastModify timestamp updated when the participant's record it was donated to, was merged into another record and the ParticipantConsId field was updated on the gift record.

Has anyone else experienced something similar?

Tagged:

Answers

  • Will Hull
    Will Hull Blackbaud Employee
    Tenth Anniversary Name Dropper Kudos 1 Participant

    Hey there, @Szymon Zaleski

    Thanks for posting your question. I actually had a client of mine recently have this same exact thing happen with their RE data sync that had a recurring gift processing, but when there was a merge, the sustaining/recurring gift remained on the discarded record that was marked as "inactive/removed" after the merge.

    In order to account for the issue, given it has happened with your data sync as well, I recommend filing a case at Blackbaud Support at https://support.blackbaud.com so that they can register the issue, if they haven't already, and identify a root cause and resolution to the issue, so that it doesn't happen again for your data as well as other organizations doing the same thing with their data in merging records.

    I hope you find this response helpful.

    Thanks,
    Will

Categories