Copying a TeamRaiser: How does the copy know when to replace the parent's ID with its own?

Mark Kindy

I know that, for now, the context-aware "0" designation for a TeamRaiser event's ID is not working in the "follow-up" autoresponders in TeamRaisers (and perhaps other places that escape me at the moment?).

I had been under the impression that the TeamRaiser's ID was considered a special string in all circumstances -- so, for instance, if my TeamRaiser's ID were "12345", and the string "12345" appeared in the content of my child blueprint or child event, that the "12345" would be replace with the child's ID.

However, this seems not to be the case; the TeamRaiser ID only gets changed when the parent's string is encountered in certain syntaxes. If my child event is ID "67890", then the string "fr_id=12345" (such as might appear in a URL) will be replaced with "fr_id=67890"; or, if used in a session tag such as "[[S42:12345:sec-cat]]" (or the XML equivalent), it will be replaced with "[[S42:67890:sec-cat]]".

My question is, is there a list of contexts or regular expressions where the ID will be replaced when it's encountered? As mentioned, I had thought it would be replaced in all cases, so I goofed up a bit when trying to do some conditional matching with the true case resulting in the TeamRaiser's ID (something like [[?xTRUEx::x[[Some tag, I forgot which]]x::12345::]]), but in doing that and making a copy, "12345" didn't get changed to "67890".

Daniel Hartanto

Hi Mark,


the "0" has always been a hit or miss based on our past experience as well that we ended up abandoning it --  but putting the parent blueprint fr_id actually works on ours that said they got automatically converted to whatever the children fr_ids are. There are 2 ways that do so that so far been stable at least on our end:


[[E48:[[S42:12045:fr-id]]:emails-sent]]


[[S47:12045:fr_info:1:event_title]]


note:

• 12045 is an actual example of one of our parent blueprint fr_id.
• you may want to try the first one -- I know from first glimpse we might say "isn't that too redundant?"  why asking fr_id value from an already known one? but give that a try if that might change your luck
• You may want to use it in context of S-tag.. let say if you are building a hotlink to entry page; instead of having the value of href to be something like where you just hard typing the parent fr_id as shown below
  
  http://main.diabetes.org/site/TR?fr_id=12045&pg=entry  
  
  why don't do it this way and see if that works
  
  http://main.diabetes.org/site/TR?fr_id=[[S42:12045:fr-id]]&pg=entry

Couple other tips:

• Always create a new blueprint instead of copying old blueprint instances to make your blueprint -- in case if all the troubles are inherited from old blueprint version
• I would suggest putting all kind of S-tag conditional or regular on the "body" of those AutoResponders instead of at the Stationary level.
  • On our end, this S-tag application parent to child auto convert fr_id works on AutoResponder as well as Coaching emails

Thus just a thought, but let us know how you fare.


regards,

Daniel


 

Mark Kindy:

I know that, for now, the context-aware "0" designation for a TeamRaiser event's ID is not working in the "follow-up" autoresponders in TeamRaisers (and perhaps other places that escape me at the moment?).

I had been under the impression that the TeamRaiser's ID was considered a special string in all circumstances -- so, for instance, if my TeamRaiser's ID were "12345", and the string "12345" appeared in the content of my child blueprint or child event, that the "12345" would be replace with the child's ID.

However, this seems not to be the case; the TeamRaiser ID only gets changed when the parent's string is encountered in certain syntaxes. If my child event is ID "67890", then the string "fr_id=12345" (such as might appear in a URL) will be replaced with "fr_id=67890"; or, if used in a session tag such as "[[S42:12345:sec-cat]]" (or the XML equivalent), it will be replaced with "[[S42:67890:sec-cat]]".

My question is, is there a list of contexts or regular expressions where the ID will be replaced when it's encountered? As mentioned, I had thought it would be replaced in all cases, so I goofed up a bit when trying to do some conditional matching with the true case resulting in the TeamRaiser's ID (something like [[?xTRUEx::x[[Some tag, I forgot which]]x::12345::]]), but in doing that and making a copy, "12345" didn't get changed to "67890".

 

 

Mark Kindy

Daniel Hartanto:

Hi Mark,


the "0" has always been a hit or miss based on our past experience [...]

Hi Dan! That's what I wound up doing, just did a find-and-replace on the ID# in the code to make it [[S42:12345:fr-id]], which, as you say, is a bit redundant, but works.

I was more just wondering if there was an affirmative list of the patterns that the TeamRaiser tries to match against, more for my own edification – though, I haven't had much trouble with the wildcard "0", except on the follow-up autoresponders and the coaching emails (I think?). Who knows what magical string-manipulation tricks we could come up with if we knew what the matching expression was?

Also, per your not re: creating a new blueprint – this was part of a tiered system, rather than creating a new one (let national create the primary framework, then have each regional branch copy the master and make edits to unlocked content, then create events off their regional blueprints).

P.S. – I'll probably take a gander this weekend and see if I can suss out what the matching expression is by creating a bunch of simple test cases.

Mark Kindy

So, after some testing (and some delays), here are the underwhelming results:

The ID# of a TeamRaiser will be updated, upon copying said TeamRaiser, in the following circumstances:

1. The ID# is used in a valid, properly constructed S-tag;
2. The ID# is used in a string formatted as "fr_id=NNNNN", where NNNNN is the ID# of the parent TeamRaiser. This replacement operation occurs regardless of the text surrounding "fr_id=NNNNN"!

Those are the only two ways the replacement takes place.