Users report that a large quantity of constituent updates appear in the Raiser's Edge Luminate Online (RELO) plugin. For many of these records, the only update is a change or new value to the Raiser's Edge Alias field Luminate Username.
Some users report this behavior shortly after going live with the RELO integration, after completing a large global change in the database, or sending emails to many recipients from Luminate Online. For investigative purposes, users can navigate to Luminate, Constituent 360 module and select the Interactions tab to compare the time of the RELO update to any changes to the constituent record. The Interactions feature in Luminate does not always carry update but in some cases is a good tool for verifying any activity on a record.
If there is no username/password in the associated Raiser's Edge record (RE, Constituent record, Alias button) and the incoming RELO update contains a username/password update these are considered valid updates that need to be processed into Raiser's Edge. The primary reason for this is that a subsequent merge of these constituents has the potential of locking a user’s Luminate account by keeping the incorrect username or password from the merge (depending on the direction of the merge). Updating the username and password in Raiser's Edge is the only sure way to avoid this problem.
How to handle high volume in RELO Using the filters in the RELO plugin can help users prioritize updates in a more efficient manner. Users can navigate to the Constituent Information button and select the Filters feature to process records with pending gifts or filter by date range. Users can also navigate to Gifts and Registrations button first and use the many filter options here. Note that any gifts tied to new records will be 'locked' until the constituent update is processed. Once these are processed the gift will be available for processing.
Check out the RELO Community to post in the discussion section and see what other processes RELO users have implemented.