michellechopin

Thanks for the clarification and validation @SanfordWhiteman! That makes sense about multiple scripts working independently - I would expect the tokens to share the same scope across whichever scripts are in the email; I was concerned that they would interfere with one another in some other way simp...

I'll try using TextEdit next time (I'm on a Mac) or see if there's a better tool for working on code, as those are tiny things that my untrained eye would never notice (and would cause me to lose my mind when something breaks 😝).

@SanfordWhiteman I appreciate you and your support, thank you! I was editing this script in Notes and I couldn't work out how to change between curly vs straight quotes - apparently that tool does it automatically as I watched it change as I typed in " (it looks like it's auto-italicising them). I p...

I think I have it! With all those details in mind, I've removed the redundant fields, added sets, and referenced those sets in place of the list of fields (and hopefully captured the logic correctly too). Would you be so kind as to take a look at the script and let me know how it looks: ## Determine...

Got it - and this all makes sense! I'm adding the various sets at the top of the token (going to use them for the couple of places where there are a lot of options). How do I reference the set later on in the script? Would I use a command like this:$lead.Support_Type__c.equals("Gold Success Plan")A...

Excuse the noob question but what do you mean when you say I'm "not outputting any fields"? I'll go through and connect the fields from the list to make sure everything is pulling in properly but will remove the {} as I go!

It makes for a VERY long script, I agree! With your suggestion in mind, where does the #set section fit in the PubSec area? Additionally, question in terms of how to read the script - does $lead.Account_Owner_Sales_Segment__c with no detail specified just mean that it's looking for a record with tha...

Given that I have a LOT of fields to update in here, what option is best? I don't want to remove them all and then have to add them back in (or vice versa) 😛

Extra question for you @PeeyushSachdeva - when I pull the field from the side menu into the editor, it shows up with curly brackets. If I pull all the fields into their respective spots, is it safe to assume the best practice is to remove those curly brackets? For example: The text you cleaned up: $...