Equivalent to the Message Catalog for specific TeamRaisers?

Options

I have a set of TeamRaisers which are all using a standard boilerplate which includes a link to a document, but the document itself is different depending on the event.  While I can swap out this link using conditionals, that is a lot clunkier than what the Message Catalog could potentially accomplish, containing a specific string which is just a URL to a specific event's document.  However, the Message Catalog is a system-wide thing.  Is there anything like this at the TeamRaiser level?  I could have a specific key, event_document, in each TeamRaiser, which has its own URL content, and then populate it with something like...

<a href="[[M0:teamraiser:event_document]]">

 

This would be super handy. I can already sort-of achieve this by cannibalizing unused fields on the TeamRaiser Pages in the Custom Pages section of the TeamRaiser buildout, using [[S47]] to reference the fields, but there isn't a way to arbitrarily add new fields to those pages (unless there is -- please tell me if so!)

Tagged:

Comments

  • Mark Kindy:

    I have a set of TeamRaisers which are all using a standard boilerplate which includes a link to a document, but the document itself is different depending on the event.  While I can swap out this link using conditionals, that is a lot clunkier than what the Message Catalog could potentially accomplish, containing a specific string which is just a URL to a specific event's document.  However, the Message Catalog is a system-wide thing.  Is there anything like this at the TeamRaiser level?  I could have a specific key, event_document, in each TeamRaiser, which has its own URL content, and then populate it with something like...

    <a href="[[M0:teamraiser:event_document]]">

     

    This would be super handy. I can already sort-of achieve this by cannibalizing unused fields on the TeamRaiser Pages in the Custom Pages section of the TeamRaiser buildout, using [[S47]] to reference the fields, but there isn't a way to arbitrarily add new fields to those pages (unless there is -- please tell me if so!)

     

    It is possible to add custom fields to the greeting page so that you can reference them with S47, however, those additional custom fields can only be added by Blackbaud, and there would be a cost associated for that customization. If you're interested in pursuing that, I'd talk to your Customer Success Manager so they can get you an estimate on the level of effort required.

  • just tips -- You can still optimize the cannibalizing approach of such unused fields :)) .. by adding your own delimiters


    Those S47 field usually holds about 255 max character, and sometimes what I did is put delimiter that you could then translate that into JS array, thus one field could holds multiple data/references to something wanted to use to build thing dynamically into different placeholders

    This approach we used it to display the honoree pictures  and link to their personal pages and render Reception and Dinner time within each event greeting/landing page in similar fashion shown on actual i.e.
    http://diabetes.org/foty
    http://main.diabetes.org/site/TR/FatheroftheYear/FOTYContent?pg=entry&fr_id=11915​


    24ae1d4195d54b118b0cdd5f59d5b1c2-huge-s4


    Or alternatively, build a Custom Page within that Teamraiser with text delimiter data (this would hold more characters beyond 255) and which you could also train/delegate your event managers to personalize that themselves through the (Event Management Center -- which is related to your other post/question)
    This one we used it build route table data containing the miles for our cycling events i.e. : http://main.diabetes.org/site/TR/TourdeCure/TourAdmin?fr_id=11705&pg=entry 

    69afd6a28492aa9ed8761988c279aea4-huge-tr




     

    This would be super handy. I can already sort-of achieve this by cannibalizing unused fields on the TeamRaiser Pages in the Custom Pages section of the TeamRaiser buildout, using [[S47]] to reference the fields, but there isn't a way to arbitrarily add new fields to those pages (unless there is -- please tell me if so!)

     

     

  • Additionally as alternative to the above delimiter approach -- branching from your other post question  @ https://community.blackbaud.com/forums/viewtopic/12/32795


    You might probably want to try upload JSON file into that document listing (just thinking out loud at moment), and should likely be able to parse it back into a LO pagebuilder through jQuery or AngularJS..probably build a widget that would translate the non-tech folks input into JSON file where you/they could upload them into the EMC Document listing, and you call them programmatically given that all files follow the naming convention to accomodate the very purpose.


    Last not least idea wise -- you could also tap into Drupal 8 "Headless Approach"-- it comes with REST service that basically you could use to replace the EMC (in case if your LO doesn't come with that), and you could parse back JSON feed from your Drupal 8 into Luminate Online pagebuilders which you could embed anywhere (within TR, or outside TR etc) you wish like this example single LO pagebuilder application with Drupal:

    http://main.diabetes.org/site/PageServer?pagename=Drupal8_REST_API_DH&showFeat=y&masonry=y
    http://main.diabetes.org/site/PageServer?pagename=Drupal8_REST_API_DH&nid=all&masonry=y


    regards,

    Daniel

Categories