Associating multiple events to a single TR

Options

Is there any downside to having more than one TeamRaiser associated with a single teamraiser? I'm concerned that there may be issues with donation history or contacts being corrupted.

Tagged:

Comments

  • Not sure what you're asking...  Are you talking about Previous Event Affiliation (Links this event to a previous event to provide returning participants with access to their Personal Page and donation history) or Event Affiliation (Determines if this event will be part of an affiliated set of TeamRaisers events that can roll up their fundraising statistics together in special status indicators and certain reports)?

  • Chris Backus:

    Not sure what you're asking...  Are you talking about Previous Event Affiliation (Links this event to a previous event to provide returning participants with access to their Personal Page and donation history) or Event Affiliation (Determines if this event will be part of an affiliated set of TeamRaisers events that can roll up their fundraising statistics together in special status indicators and certain reports)?

    Talking about Previous Event Affiliation.
  • Josh Weinstein:
    Talking about Previous Event Affiliation.

    Here's one implication that we JUST discovered this week.

     

    We have a yearly event, and each one is associated with the previous year.

     

    Our 2013 version is live now, and we are working on your 2104 version now. 2014 is published - since Convio has no concept of a staging environment, it must be to test. The in-progress 2014 was already associated with 2013 as part of it's set-up.

     

    So a participant in 2013 sent out an email asking for people to join his team. He used the exact same email content as he used in 2012 - so his email sent a link to the *closed* 2012 version.

     

    Turns out Convio automatically forwards that page to the NEWEST associated event, bringing the email recipient to our totally-haven't-told-anyone-about-it-yet 2014 version, rather than the 2013 version. So out of the blue we have a public registration for our in-progress TR.

     

    The easy solution is not to associate a TR with the previous year until it is ready-to-go, but who knew?!

     

     

    Otherwise, I think all this controls is the registrants ability to recover/migrate their registration set-up from the previous year.

  • Brian Mucha:

    Here's one implication that we JUST discovered this week.

     

    We have a yearly event, and each one is associated with the previous year.

     

    Our 2013 version is live now, and we are working on your 2104 version now. 2014 is published - since Convio has no concept of a staging environment, it must be to test. The in-progress 2014 was already associated with 2013 as part of it's set-up.

     

    So a participant in 2013 sent out an email asking for people to join his team. He used the exact same email content as he used in 2012 - so his email sent a link to the *closed* 2012 version.

     

    Turns out Convio automatically forwards that page to the NEWEST associated event, bringing the email recipient to our totally-haven't-told-anyone-about-it-yet 2014 version, rather than the 2013 version. So out of the blue we have a public registration for our in-progress TR.

     

    The easy solution is not to associate a TR with the previous year until it is ready-to-go, but who knew?!

     

     

    Otherwise, I think all this controls is the registrants ability to recover/migrate their registration set-up from the previous year.

    I think you are correct, Brian, but I wanted to know for sure. Thanks!

Categories