Duplicate gifts can occur in the plugin from a variety of causes including editing processed gifts, delayed processing, or merging constituent records. Ensure you are on version 1.4.5465 or above of the Luminate Online plugin. If the issue persists explore the following:
1. This issue can be caused when gifts are missing the Luminate Online Gift ID attribute, or missing the value for that attribute which is usually a 4 to 6 digit number (the last 4 to 6 digits of the confirmation code on the gift in Luminate Online). The plug in uses this data to determine if the gift already exists in the database, so if it is missing, it's possible for gifts to download more than once. Ensure that all gifts that are downloaded into Batch from the Luminate Online plug in have this attribute with the 4 digit number. If they are missing the attribute, look in Luminate Online for the confirmation code and the last 4 digits, and query the database based on that number. If the gift is not yet in the database, manually enter the 4 digits into the Luminate Online Gift ID attribute description in Batch before committing.
Check for duplicate gifts by creating a Raiser's Edge Gift query with the following criteria:
Gift Information > Gift Date between [possible range affected]
AND Attributes > Specific Attributes > Luminate Online Gift ID > Luminate Online Gift ID Description not blank
Users can then output:
Attributes > Specific Attributes > Luminate Online Gift ID > Luminate Online Gift ID Description
Sort by the same field and view the results to look for any potential duplications. On the gift, go to File > Properties to find the Batch number. Access the batch and note if the Luminate Online Gift ID attribute is missing or incomplete. The duplicated gifts may then be deleted after confirming they are duplicates. Ensure The Raiser's Edge has a current and useable backup before deleting anything from the database.
2. If a constituent record with any history of gifts or registrations was recently merged, users must allow the integration enough time to process the merge and constituent history and update/remove duplicates transactions sent to the plugin. RELO cleans up duplicates when the plugin is loaded or when "Constituent information" or "Gifts and registrations" are closed. If duplicates are found in the plugin, close the application, navigate to another area of the database to allow time for the cleanup process to complete and navigate back to the plugin to continue working.
3. Best practice to prevent duplicates is to process updates and transactions from the plugin as soon as possible. Database cleanup and merging duplicate constituent records outside the plugin should be done after all transactions have been cleared from the plugin, if possible.
Connect and collaborate with fellow Blackbaud users.