TeamRaiser Coordinator pulling into Thank You Autoresponders but now Follow Up Auto Responders

Randy Tolentino

Hello Everyone,

 

I'm hoping that everyone is prepared for an awesome Thanksgiving!

 

I'm having a bit of trouble. We have a TR Blueprint that, in some Autoresponders is trying to pull the Event Coordinator info (name, email). 

 

I'm including this code in the signature:

 

[[E47:[[S42:0:fr-id]]:fr_info:1:coordinator_name]]
[[E47:[[S42:0:fr-id]]:fr_info:1:coordinator_email]]

 

In a Child Event of this Blueprint When receiving Thank You for Registering / Thank You for Forming a Team, the Event Coordinator info is dynamically populated. However, when receiving First, Second, and Third Follow Up messages, it's wiped out and nothing is appearing.

 

Does anyone know why it would work in the Thank You AR's and not the Follow Up AR's? (this is within the same AR series)

 

 

In addition, I recreated a similar situation in our Sandbox instance and the code/tag does work there for both the Blueprint and Child Event.

 

 

Any help or insight would be greatly appreciated.

 

 

 

Happy Thanksgiving

 

 

Randy Tolentino

Associate Web Developer | Charity Dynamics

rtolentino@charitydynamics.com

 

 

Hilary Engelbrecht

Hey Randy, 

 

Did you ever get an answer here? 

 

I'm having a similar problem in that my blueprint preview pulls in the information but my child events do not. Any idea on that one? 

 

Thanks!

Hilary

Randy Tolentino

Hilary Grunewald:

Hey Randy, 

 

Did you ever get an answer here? 

 

I'm having a similar problem in that my blueprint preview pulls in the information but my child events do not. Any idea on that one? 

 

Thanks!

Hilary

Hi Hillary,

 

Yes, we got it to work by changing the s-tag...

 

What we're doing now is hard-coding the fr_id into the tag, in the Blueprint... then when you push the changes, the child-events will know to populate their own fr_id's in that tag.

 

Our new tag looks like this:

 

[[S47:XXXX:fr_info:1:coordinator_name]]
[[S47:XXXX:fr_info:1:coordinator_email]]

 

So, try this:

 

1. Ensure that all coordinator information is entered in the Custom Pages >> Greeting >> Coordinator fields

2. Use the code above and hard-code your Blueprint fr_id into those tags (for example: [[S41:1234:fr_info:1:coordinator_name]]

3. Push changes

4. What you can expect is that in the child events, the fr_id (XXXX) will be automatically populated like this: [[S47:1235:fr_info:1:coordinator_name]] or [[S47:1236:fr_info:1:coordinator_name]]

 

 

That seemed to work for us.

 

Good luck!

Hilary Engelbrecht

Randy Tolentino:

Hi Hillary,

 

Yes, we got it to work by changing the s-tag...

 

What we're doing now is hard-coding the fr_id into the tag, in the Blueprint... then when you push the changes, the child-events will know to populate their own fr_id's in that tag.

 

Our new tag looks like this:

 

[[S47:XXXX:fr_info:1:coordinator_name]]
[[S47:XXXX:fr_info:1:coordinator_email]]

 

So, try this:

 

1. Ensure that all coordinator information is entered in the Custom Pages >> Greeting >> Coordinator fields

2. Use the code above and hard-code your Blueprint fr_id into those tags (for example: [[S41:1234:fr_info:1:coordinator_name]]

3. Push changes

4. What you can expect is that in the child events, the fr_id (XXXX) will be automatically populated like this: [[S47:1235:fr_info:1:coordinator_name]] or [[S47:1236:fr_info:1:coordinator_name]]

 

 

That seemed to work for us.

 

Good luck!

Thanks! 

 

Question - why are S47 and S41 tags used in your example? I think it's supposed to be S47, but just want to make sure. 

Randy Tolentino

Hilary Grunewald:

Thanks! 

 

Question - why are S47 and S41 tags used in your example? I think it's supposed to be S47, but just want to make sure. 

Embarrassing - you're right, it should be a S47!