New TeamRaiser participant search kicks you into old TeamRaiser

Kim Ethridge

We have an ongoing TeamRaiser that's a general DIY fundraiser. We are now creating a second TeamRaiser for a brand new event. Both TeamRaisers will be live at the same time. On our new TeamRaiser the Search for a Participant takes you back to our original DIY TeamRaiser the those participants. I'm just trying to do some background troubleshooting for our front-end developer who has a case open with Blackbaud. Wondering if anyone else who has created multiple TeamRaisers has run into this issue.


Thanks for your help.


Kim

Jon Reich

Hi, Kim! Try adjusting the Participant Search Parameters by following this path in the TeamRaiser configuration:

3. Select Event Options > Edit Advanced Options (left side menu, but under "Related Actions" at the very bottom) > b. Define Event Options > 18. Participant Search Parameters


Hope that points you in the right direction!


- Jon

  --

Jon Reich * Partner * Cathexis Partners * jon@cathexispartners.com * p.605.377.8147

Kim Ethridge

Jon Reich‍ - We've already selected " People can search for participants registered for this TeamRaiser event only Kim

Jon Reich

Thanks, Kim! When you go to the search page... does the fr_id in the URL change to the old TeamRaiser? I wonder if that button is hard-coded to go to that specific TR. That's the next place I'd look. - Jon

Kim Ethridge

No, oddly it goes to https://secure.cbf.org/site/TR

Jon Reich

Hm... what's the main/entry link for the new TeamRaiser? - Jon

Kim Ethridge

Jon -

https://secure.cbf.org/site/TR?fr_id=1110&pg=entry

Jon Reich

Thanks, Kim. I did some test searches (including just hitting search w/out entering anything to show all), but everyone I tried only returned participants for the same FR_ID 1110 TeamRaiser. That seems to be functioning as desired/expected. Are you still seeing results from the other TR show up? Thanks! - Jon

  --

Jon Reich * Partner * Cathexis Partners * jon@cathexispartners.com * p.605.377.8147

Kim Ethridge

Thanks, Jon. Looks like our frontend developer figured it out with support.


Kim