It would definitely save me some work if this were possible.  Our use case - some accounts have CSMs and AMs assigned and some just have AMs.  When we send emails to the customer, they can come from the AM, and we’d like to CC the CSM in the cases where there is one.  Today, I have to build two separate queries - one for accounts with a CSM and one for accounts without to get around this.  Would be great if I could just build one, and use the CSM if it exists in the CC field.

Hello @alex_legay  @heather_hansen 
We will look into this.

+1 to this. We have a situation where an onboarding email needs to be sent to one primary contact but we also wanted to give an option to add more onboarding contacts that can be cc’ed. Because the mapped additional onboarding contact couldn’t be null, we had to drop this idea. I can see many use cases where this would be valuable. 

@chethana Could we convert this into an idea so we can vote? Thanks!

Curious where this stands with new dynamic programs. In theory, @heather_hansen’s workaround (below) should work in the new dynamic JO to combine those two programs into one by using an evaluate step to check whether the CSM is null, and send the appropriate version, but the best solution would be if we could have that logic within sender/reply-to/cc/copy fields, so we didn’t need different templates or programs to account for null fields (if CSM not null, CC, else, just send).

@dayn.johnson @heather_hansen The solution suggested worked with the new dynamic JO to combine the two programs into one by using an evaluate step to check whether the CSM is null.

However, the CC option did NOT send the email to multiple recipients. When I added both CSM and Sales in CC, the CSM received the email but Sales didn’t.
Have you faced similar issue? Please suggest a possible solution.
Thanks in advance.

@ganesh.patil, unsure on the best solution here, but the below may apply to your issue.

Another point here -- this becomes an even bigger issue when there are multiple contacts in the CC field, and any one (or multiple) of those may be null. The only good way to get around this is to do multiple templates, each with a different combination (ex: CSM and AM are not null, Sales rep is null), to account for each different permutation -- and have each of those as a separate branch in the program.

Yes, data hygiene is important, but sometimes there are cases where there is legitimately no rep.