Luminate Online integration
Luminate Online integration allows you to review and resolve issues for records and changes that have not properly synchronized between Luminate Online and Raiser's Edge NXT.
Tip: Use Luminate Online integration instead of Queue Problem Management in Luminate Online. While some issues may show in Queue Problem Management, you'll now use the interface in Raiser's Edge NXT to work with data sync issues.
Errors can be a result of differences between Luminate Online and Raiser's Edge NXT data fields. To manage errors, go to Settings, Control Panel, and select Luminate Online integration. From there, you can select:
-
View to open the category errors.
-
Links to review further information.
-
Delete to remove the error from this portal. This does not resolve the error.
-
Retry after resolving the issue to process the sync.
Below, we've included common errors and possible resolutions. This information does not cover all errors or recommended resolutions due to each organization's unique configuration.
Constituent errors
| Error message | Reason error occurs | Resolution |
|---|---|---|
| ConsInvalidAttributeValueException | Data moving from Raiser's Edge NXT to Luminate Online is invalid according to constraints. For example, a name field that is greater than 50 characters. | Update the Raiser's Edge NXT record to correct the problem and then select Retry. |
| Constituent not found | The constituent record in is Inactive but the inactivation did not occur in Raiser's Edge NXT. | Delete the record in Raiser's Edge NXT, and then delete the message. |
| Constituent Inactive; Cannot make changes | The constituent record in is Inactive but the inactivation did not occur in Raiser's Edge NXT. | Delete the record in Raiser's Edge NXT, and then delete the message. |
| cv.UniversalDeserializeException | The record contains a member_id that no longer exists in Raiser's Edge NXT. | Mark the record in as Removed, or unlink the record in so it creates a new record in Raiser's Edge NXT. |
| Message Rejected | The links between and Raiser's Edge NXT records are not consistent. The record is linked to a Raiser's Edge NXT record that is linked to a different record. The Local ID version conflicts with the actual value. | Contact and work together to fix the links. |
| Missing required field: last_name | A Last Name value is missing from the reported records, but Raiser's Edge NXT requires last names. The error occurs in when constituent records do not have last names. | Add a last name to the Luminate Online records and then select Retry. |
| Must provide an existing Contact for this action | A contact update fails to synchronize because the contact was deleted in the Raiser's Edge NXT but left active in Luminate Online . | Mark the constituent Inactive in . If the constituent needs to be Active, then it may be possible to clear out the Member ID and External Revision ID in and synchronize the record across as a new contact. |
| TooManyTransientFailures | A network communication error occurred with Raiser's Edge NXT or a contact record has not synchronized and there are message dependencies in which other data needs to be synchronized first. | Correct the problem described in the Message Log or message XML and then select Retry. |
| UnexpectedHTTPStatusExceptions | A temporary network glitch occurred. | Select Retry. |
Event errors
| Error message | Reason error occurs | Resolution |
|---|---|---|
| F2FException | This generic exception message can occur for many reasons. For example, the system is unable to find a team by ID because the team was deleted in Luminate Online but not deleted in Raiser's Edge NXT. | Check that TeamRaiser Team Captain and Registration exist and are cross referenced correctly. |
| MissingContactReference | The contact failed to synchronize, possibly due to an error. Whatever is synchronizing across with the contact has synchronized first. | Check the contact queue for errors. Resolve the errors, then select Retry. |
| MissingEventTicketClassXrefException | Occurs when the event ticket class isn't cross referenced in Luminate Online. | Cross reference the ticket event in Luminate Online. |
| MissingTRCampaignXrefExceptions | This occurs when the TeamRaiser campaign isn't cross referenced to Luminate Online. | Cross reference the TeamRaiser campaign in Luminate Online. |
Fundraising errors
Other errors
| Error message | Reason error occurs | Resolution |
|---|---|---|
| Com.convio.bus.UniversalFieldMapperException: Unable to locate refund data for transaction ID xxxxxx | This is error occurs when a gift amount is reduced manually instead of using the refund process. | Contact Blackbaud Support |
| Luminate Integration not configured or improperly configured | Queue activity is disrupted. | In Luminate Online, go to Data Management, Luminate Integration to check the configuration, then select Retry. See Configure Luminate Integration for information. |
| No cross reference defined | Cross-references are not properly configured or confirmed. | Define missing cross-references and click Requeue. |
| SOAPFaultException | The batch failed to process. | Contact Blackbaud Support. |
| Unable to parse relationship details for TeamRaiser gift | A cross-reference is missing. | Create the cross-reference and click Rebuild. Click Reissue if cross-reference was not updated. |