Wyatt_Bales4

Thanks for the response, Sanford. It's not a matter of crossover but a matter of not populating when there's a duplicate. For example, if I have a simple $object.attribute in an email pulling from a Custom Object, it will not display any value in the email if there is a duplicate record in the datab...

Thanks for the response, Greg. We use various custom objects ranging from transactional nature (e.g. order history) to a reference table (e.g. onboarding status). The dedupe fields are usually a custom row ID with the link field either being email address or SFDC ID.As for the scripts, some are #for...

A question I'm sure Kiersti Esparza​ may be familiar with.

Removing the .get(0) or checking to ensure there's no duplicate record with a matching email address are two steps maybe to try as well.

Thanks for the tips, Sru. Actually ended up using a similar constraint on the custom object (a date field). I think your additional 2 recommendations will help narrow things down should this design also lead to poor performing scripts. I'll post back once we have some more testing under our belt.

I've already tried using similar unique qualifier. The issue is, Marketo's smart list aren't only bringing back that record--it brings back the oldest version of that record. One thing I can try testing is if a duplicate record is created, backdate the Created Date on the record I want to tie the cu...

This is a new idea listed here:

Hi Jan,A quick solution we did for Montreal was to paste the English email HTML into a Rich Text object on a blank landing page. We then just link to it from our French emails. Just ensure you don't reference any email scripts.