Constituent Records getting tangled, possibly due to TR participant making online donation for a donor

Hi Jill, 


that has not happened to us  (also we have never use cash as payment type for LO donation forms -- not aware if that is part of the available payment options -- yes there is offline gift, but that is not actual donation and usually participant would manually entered that from their Participant Center when they expect to receive cash donation that has yet to go through approval/confirmation process) --  but normally in Luminate Online if you want to enable user to donate to someone, a team, or make general donation to the events -- you append the proxy URL parameters -- they are &PROXY_ID=  and &PROXY_TYPE=  (usually already built onto the out of the box donate links within Teamraiser pages but you could replicate the link in case if you need to make your own buttons, or provide the links somewhere else) and there is no need to add custom fields to hold donor info etc because those proxy parameters would automatically put the donation accordingly to show on fundraising progress / reporting purpose.


Without further ado, here are the templates (Note: replace the red with your actual values (i.e. actual domain name, actual dfid (which is your donation form id), frid (a.k.a event id), consid, team id accordingly;  Also note different "Proxy Type" value for these 3 types.)

Donation to someone


https://YOUR-DOMAIN-NAME/site/Donation2?df_id=DONATION-FORM-ID&FR_ID=EVENT-ID&mfc_pref=T&PROXY_ID=CONSID-OF-PARTICIPANT&PROXY_TYPE=20&DONATION-FORM-ID.donation=form1


Actual example: https://donations.diabetes.org/site/Donation2?df_id=18982&FR_ID=11704&mfc_pref=T&PROXY_ID=9267426&PROXY_TYPE=20&18982.donation=form1​




Donation to a team


https://YOUR-DOMAIN-NAME/site/Donation2?df_id=DONATION-FORM-ID&FR_ID=EVENT-ID&mfc_pref=T&PROXY_ID=TEAM-ID&PROXY_TYPE=22&DONATION-FORM-ID.donation=form1


Actual Example: https://donations.diabetes.org/site/Donation2?df_id=18982&FR_ID=11704&mfc_pref=T&PROXY_ID=739426&PROXY_TYPE=22&18982.donation=form1​



Donation to the event in general


https://YOUR-DOMAIN-NAME/site/Donation2?df_id=DONATION-FORM-ID&FR_ID=EVENT-ID&mfc_pref=T&PROXY_ID=EVENT-ID&PROXY_TYPE=21&DONATION-FORM-ID.donation=form1

 

Actual Example: https://donations.diabetes.org/site/Donation2?df_id=18982&FR_ID=11704&mfc_pref=T&PROXY_ID=11704&PROXY_TYPE=21&18982.donation=form1




hope that helps,


regards,

Daniel


 

Jill Freidmutter:

Dear Wise Ones,


Has anyone had a similar experience and can shed light on how to avoid it? We have had a few instances where a TeamRaiser


TeamRaiser participant receives a cash donation. The participant goes online to give that donation via credit card (billing info) for the donor (donor info). The participant record, the donor record and the gift get mixed up together. We've had this start in different configurations (using donor's credit card info or participant's credit card info) and land in different configulations:

-- The donor's name takes over the participant's record.

-- The participant's record shows the gift.  

-- and on...


Information seems to cross record boundaries. Has anyone else out there faced this? What was the resolution? I am working with LO support, but resolution is taking longer than I had hoped, and any additional clues are welcome.


Thank you! Jill


 

Thanks for reclarifying Jill, unfortunately we are not using RE (was responding initially thinking this was about TR alone) probably I myself not going to be of any help especially if this might be pertinent to the RE LO plugin

Jill Freidmutter:

I'm not sure that I conveyed what I was hoping to, so let me try again briefly. The cash donation wasn't to us but to the participant. The participant made an online credit card donation for a donor that was not her. The LO constituent records seem to get jumbled, especially names / gifts / participations.


Okay, here is a not-so-brief example:

1) There are two records in RE: 
     a) Jane Smith, RE Constituent ID 2017-12345, created 8/2/17, Address XYZ 
     b) Jane and John Smith, RE Constituent ID 11111, created 12/22/2000, Address ABC 
2) There are two records in LO: 
     a) Jane Smith, LO ID 99999, created 1/5/2017, with all the transactions, Address XYZ 
     b) Jane Smith (Mr. and Ms.), LO ID 22222, created 8/2/17, with no transactions, Address ABC 

There is a mixture of information between the records – not a one-to-one mapping. This is what I mean by the records getting jumbled. 
• 1a and 2a: 
     o Both are records for Jane and spouse 
     o Both have same address: Address ABC 
• 1b and 2b: 
     o Both are records for Jane individually 
     o Both have same address: Address XYZ
• 1a and 2b: 
     o Both have $5 gift dated 8/2/17 
     o Both have creation dates 8/2/17 
• 1b and 2a: 
     o Both have $50 gift dated 8/2/17 
     o Both have creation dates prior to 1/6/2017 

In RE, the participant registration landed in the original record on 4/24/2017, which leads me to think the participant registered in the joint LO record. 
I have the sense that in LO, when the constituent was brought through the RELO plugin into RE, somehow the two records in LO were switch/merged into the new record, but with the old creation time attached to it. 

If the participant goes to the regular teamraiser donation form, then it's correct that they are probably still logged in which puts the donation on that participant's record. That overwrites their billing address and other stuff too. You can see what happeded and unravel it on the interactions tab. Click 'Show All'.


I wouldn't use Megan's script though, because it would automatically log out everyone - making it impossible to make a logged in donation. Donors give more than once and have cookies too.


I suppose you could add a check to see if they are a participant instead.


https://www.blackbaud.com/files/support/helpfiles/luminate-online/help/luminateonline.html#../Subsystems/S-Tags/Content/S-Tags/S48_TeamRaiser_Participant.html


[[?xx::x[[S48:1234:part-type-id]]x:: ::

<script type="text/javascript"> 

    window.location='UserLogin?logout=true&NEXTURL=[[T1:[[S8]]]]'; 

</script>  

]]


But this is still annoying, because it still boots the participant out and they won't like that either. The Participant Center has the ability to take these type of offline gifts. I don't think gifts from this form go on the participant's record - at least we haven't noticed it.




You can allow them to enter unconfirmed cash or checks, and then they sent it in to you, at which point you confirm their transaction. We don't allow that, and only show the credit card fields.