Skip to main content

I’m working on an unpublished program, and have added a new calculated field that I wanted to test but remembered after creating it that it cannot be used in variant filtering, ok no problem. Delete the calculated field. 

Then, every single action in the program had an error icon. Even wait steps. Even steps that had no connection to that field at all. In fact, none of the steps referred to that field. 

This program has 35 actions. THIRTY FIVE steps that need to be reviewed just to hit ‘Save’. It’s exhausting. 

  1. Added a new calculated field that I wanted to test but remembered after creating it that it cannot be used in variant filtering. Delete the calculated field. 
  1. Every action in the program had an error icon. Even steps that had no connection to that field at all. 

There’s two things here.

  1. This is absolutely a problem. Pretty sure I’ve heard even ​@sarahmiracle voicing this frustration. Can someone explain like I’m five why calculated fields can’t be used to filter email variants? Much easier to build that logic into a JO than having 5 (or 10) different email steps (and multiple templates where one should be able to work).
  2. This is definitely a frustration. I’d love to know the logic as to why adding a new calculated field affects unrelated steps (especially wait steps).
Terms & ConditionsCookie settingsAccessibility statement