Automating the designee of TR donation form for DIY fundraising - HELP!

Tanna Lewis

Happy Monday All!


I am hoping some lifesaver out there can help me with a tricky TR donation issue.  We have a couple of TRs we are using for DIY fundraising, and the fundraiser lets us know during registration which designation they want to support with their fundraising (through a free text registration question stored to a custom profile field).  We then need to associate all donations collected through their personal page with the designation they indicated.


Right now it is a quite cumbersome process, involving manually re-associating the gifts in BBCRM (which flow from our LO-BBCRM sync into a temporary suspense holding designation) to each fundraiser's correct chosen designation, on a daily basis. 


I would think there is a way to trigger this more automatically. Looks like the fundraiser's ID is available in the url of the donation page through &PROXY_ID=. If I can use that ID to then grab a designee ID stored in a custom field on the fundraiser's LO record and use it to trigger the autopopulation of the hidden designee field on the donation form so that the designation comes down to BBCRM normally, that seems pretty perfect. 

So basically, I am thinking the solution could be something like:

1.    default hidden single_designee to option value 1041 (as catch-all to write to suspense designation in case next step fails)
2.    grab content of custom_number1 from record of url PROXY_ID, and use it to select single_designee option with matching value #
   •    if custom_number1 null, single_designee option value=1041 (suspense)

(And as a side note, I'd handle this for our second DIY TR by having its donation form refer to custom_number2 instead.) 


I'm not sure if my solution above is possible, though, since it is not the logged-in user's custom field info I am trying to access, but instead the fundraiser's. Also I'm not so good at writing functions from scratch, so struggling to even test the theory. Do any of you amazing, knowledgeable LO peeps out there have advice on how I could do the above? Or a better solution? Anyone already do anything similar?


js/jquery and/or s-tag-based ideas welcome! Also, we are not using API donation forms, just the out-of-box donation forms, but if you think an API solution would be necessary, please let me know!


(And as a second side note, just FYI, I'll also probably change the fundraiser registration forms to have a designation choice drop-down instead of free text, to make it easier to automate that aspect as well.)


As always, thank you all SO SO MUCH!


Tanna

Tanna Lewis

Hi all!  Update in case this is helpful to anyone else doing designated DIY TR fundraising - here is what I've come up with so far.  Seems to work fine, but again, I am still a monkey-see-monkey-do js/jquery tinkerer, not formally trained yet. Would LOVE the feedback if any jquery-savvy people see issues with this!!


//default designation selection radio

$('input:radio[id=single_designee_designated]').val(['designated']);


//load in designation value; custom_number5 = Team Children's TR / custom_number6 = TCC Birthdays TR; suspense designation 1041 if custom field is empty

var TCCdesignee='[[E48:[[S334:FR_ID]]-[[S334:PROXY_ID]]:cons.custom_number6]]';

if (!TCCdesignee) {

    $('#single_designee').val('1041');

}else{

    $('#single_designee').val(TCCdesignee);

};


Screenshot shows a temporary line of text up top confirming the contents of custom_number6 for the test fundraiser, and shows that the corresponding designation has been correctly populated (though of course I will hide the designation area once this is complete).




So this is working well in feeding the designee ID from the fundraiser (as identified from PROXY_ID in the url) as it is stored in a custom number field on the fundraiser's constituent record.


Sooooo step 2: I intend to have that custom number field populate from a couple of questions on the fundraiser's TR registration form - one which is a required single-selection drop down with the friendly names of the designees we want to offer, which I will then have a bit of code translate into the corresponding designee ID # and insert into a hidden question linked to the appropriate constituent custom number field for that TR's designee.  If the desired designation isn't offered, the fundraiser can choose "other" (and fill in a note about the designation) - this will trigger our suspense designation and prompt our staff to manually review / update the custom field with the ID of the requested designation.  Still a little work, but nowhere near as bad as it has been having to edit every single donation from our DIY TRs!  Will post an update when I have that part of things set up, as well. 


Just sharing my progress so no one spends time trying to answer the initial question!  But again, would love feedback at this stage!!  Thanks all!!!

Brian Mucha

I actually built a solution for this some time ago that I call 'Designated Fundraising'. I've been lazy about documenting it enough to post here.


The TR fundraiser tells us what fund they want their donations to support, and we add them to a JSON look-up file. Here's a sample entry:


    "1924661":

    {

        "fund_id": "1588",

        "tribute_type": "memorial",

        "tribute_name": "Joshua McFadden",

        "tribute_import": "00001-602-0000040224"

    }


When the page loads it grabs the PROXY_ID from the URL, which is the team or fundraiser's participant Id, and then uses that as the key to find if they have asked for a fund and what that fund id is.


It's all done in a JQuery plugin. Here's a sample on a live form:

https://secure3.convio.net/cmf/site/Donation2?df_id=12064&12064.donation=form1&FR_ID=1720&mfc_pref=T&PROXY_ID=1924661&PROXY_TYPE=20


I use the s_debug parameter to show the normally hidden fields so we can make sure it's working. It also loads the unminimized scripts for easy debugging.

https://secure3.convio.net/cmf/site/Donation2?df_id=12064&12064.donation=form1&FR_ID=1720&mfc_pref=T&PROXY_ID=1924661&PROXY_TYPE=20&s_debug=true


Here's the plugin:


https://secure3.convio.net/cmf/_resources-teamraiser/reus_js/jquery.madFunds.js


I also have version 2 nearly complete, which allows for gifts to be split evenly between up to four funds.


BPM

Tanna Lewis

Whoa, only just seeing this today - how'd I miss this?  Sweet - thank you so much for sharing, Brian!!! 


Q: As new fundraisers register, is the update of the json file automated?

Brian Mucha

No, not automated.


We have the TR set so new registrants need to have their personal page approved by the event manager.


The registrant provides the fund designation and tribute information when registering. We have about 5 bazillion funds, so the fund_id needs to be selected by someone internally based on the registrant's description. The tribute honoree also needs to be created in RE, which then gives us the RE Import_id for that record. Then we update the JSON file and approve the user's personal page.


The fund_id and Import_Id are passed on the transaction, and then used by OMatic to automatically connect the donation to the proper fund and honoree in RE.


EDIT: A few words

Tanna Lewis

Okidok, I think I'm on a good path! Thank you again so much for sharing your plugin!!!! You da real one!

Brian Mucha

Tanna Lewis:

Okidok, I think I'm on a good path! Thank you again so much for sharing your plugin!!!! You da real one!

 

You bet. Here's the newer version I mentioned.

https://secure3.convio.net/cmf/site/SPageServer?pagename=designated_fundraising_teamraiser_test&FR_ID=1234&mfc_pref=T&PROXY_ID=1105632&PROXY_TYPE=24&s_debug=true


This one allows for split designations. It splits the amount evenly across up to four funds. The JSON looks like this:


{

    "1105632":

    {

        "fund_id_0": "1164",

        "fund_id_1": "1041",

        "fund_id_2": "1168",

        "fund_id_3": "1176",

        "tribute_type": "honor",

        "tribute_name": "Nora Mucha",

        "tribute_import": "00001-593-0000530024"

    }

}


Here's the script:

https://secure3.convio.net/cmf/_wrappers/luriechildrens/mainsite_2018/scripts/luminate-designated.js


The ghost form should use the Designated Giving Donation Level widget with four Single Drop-Down Lists configured.


Here's the form - though the user never sees it.

http://foundation.luriechildrens.org/site/Donation2?13065.donation=form1&df_id=13065&mfc_pref=T


I'd be interested if you do anything with this. Feedback is welcome too. 


B

Tanna Lewis

That is super slick!  We currently don't allow split designations in LO at all, but that being said, some of our DIY TR fundraisers do request a split, which we handle manually on the BBCRM side.  Would definitely be nice to automate that aspect as well.  However, doubtful that our LO-BBCRM integration can handle it.  So I will investigate that side of things and will def let you know how it goes!!


Also really appreciate seeing your example of configuring the donation form Designated Giving this way and your note on where to set up, since it isn't something we've offered before.  If the LO-BBCRM integration can handle it, this has some other potential future uses...


AND, ahem, didn't know about s_debug before this week and I'm liking life better since learning that lil tidbit, too.


So thank you very, very much, as always!!!

Brian Mucha

Same deal here with split gifts. This is our first use too.


That s_debug doesn't have any special function by itself in LO. It's just a normal session variable.


You can set them in the URL just like you would with [[U0:varName]] and then read it with [[S80:varName]].  So set a variable in the url like &s_foo=bar and then later read it on page like [[S80:foo]].

https://www.blackbaud.com/support/howto/coveo/luminate-online/Subsystems/S-Tags/S-Tags/S80_Value_of_Session_Variable.html


I use s_debug to do a few useful things. 


Here's a conditional for the pagewrapper to use un-minimized or minimized scripts.


[[?[[S80:debug]]::true::

<script src="../_wrappers/luriechildrens/mainsite_2018/scripts/luminate-designated.js"></script>

::

<script src="../_wrappers/luriechildrens/mainsite_2018/scripts/luminate-designated.min.js"></script>

]]


Or to show a normally hidden block (just like this form does)


<div class="[[?[[S80:debug]]::true::hidden::]]">

    Normally Hidden Stuff

</div>


EDIT: Oops! Had S80 and U0 swapped. Fixed.


By the way, the docs say that S80/U0 don't work in email but they sure do. 


The trick there is that you have to set the variable with U0 before you read it using S80 according to the DOM. So for instance you can't set it at the bottom of your stationary and then read it in the message body, because that will be out of order.


I use this particularly with emails that use reusable content for the message. Set something like Event Title in the message body right before including the reusable. Then in the reusable content you can say:


<h1>Thanks for registering for [[S80:eventTitle]]</h1>

Tanna Lewis

Ah, I see.  Thought it was LO function to show elements hidden at the form level.  But that is so cool!!  I've never thought to do that, though now that I think of it, I must have reviewed test versions of scripts which I bet were handled similarly.  That is super super useful. 


OK, I am learning too much for a Friday afternoon, Brian, stop.  Hahaha!  Have a good weekend! 


Overflowing with gratitude,

Tanna