1

I'm running tests on a Journey that uses contact data decision splits as a contact may have done desired action during the course of the journey. One of my decision splits is looking at a date field that is NULL and sending them an email if that field is NULL. However, the journey doesn't handle the record properly and puts them down the remainder path.

The other decision splits that look at fields and whether they are NULL are working (but they are text fields).

  • Update - the date field is now working. It's now only the last decision split based on whether an attribute is NULL or not. It's a text field. – Tom Callahan Mar 27 '18 at 17:33
  • Update - after further testing...It seems to be working now. Don't really know if this is an intermittent issue, or not. – Tom Callahan Mar 27 '18 at 19:35
1

I see that you got things working, but wanted to say that I've gotten in the habit of using (Field IS NOT NULL OR Field != ''). I was told by support that empty fields does not necessarily mean NULL.

| improve this answer | |
  • This is helpful, no doubt. I'll likely implement this vs. what I'm currently doing. I think the major issue here is that Marketing Cloud doesn't prescribe NULL on a field that is NULL but leaves it blank, causing users to misread a field that is empty vs. a field that is actually NULL – Tom Callahan Mar 27 '18 at 20:34
  • @TomCallahan, One issue among many, I'm afraid >_< – user43881 Mar 27 '18 at 20:46
  • How do you look for an empty string in the decision split filter criteria wizard? Do you literally put 2 tick marks in the text field? Just a space? It won't accept leaving it completely blank. – Nick Nelson Nov 28 '18 at 18:04

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.