Please submit all product enhancement ideas below. We welcome your feedback; your ideas will be reviewed by the Product Manager that oversees the development of that part of the product on an ongoing basis and updated with its current status monthly based on our product planning process. Ideas you submit could help us shape features currently in development or grow our repository of requirements for our next big enhancement. Thank you for taking the time to share your thoughts and expertise with us.
If you believe you are experiencing a defect please contact Support.
Currently all registrations are being synced into the Events Module in RE as “Registrants”. This makes it impossible to tell who is a primary registrant versus a secondary registrant in RE. The current solution to this issue would be to create a report in LO to determine the username that added the secondary registrant – then manually look up a constituent by the username to determine who paid for the secondary registrant. This creates a cumbersome task that monopolizes a lot of time for database teams when preparing for an event.
Please consider changing the integration to add only primary registrants as “Registrants”, and add secondary registrants as “Guests” in RE’s Event’s Module; with the primary registrant’s record linked into the guest record for the field “Guest of”.
Privacy Policy | Safe Harbor Notice | Terms of Use | Acceptable Use Policy | © 2019 Blackbaud, Inc. All Rights Reserved
Hi Austen,
Did you find any other way around this? I'm having the same problem. This is a good potential solution. Even a report within Luminate would be helpful. I like this more though because I hate having to open BBMS, Luminate, RELO and the event module and still be unable to connect primary and secondary registrations.