I am having troubling configuring a Decision Split in a journey with SF Campaign Member object as the entry event. The entry source includes the campaign ID via CampaignMember:Campaign:Id.

In the Decision Split, I added a attribute-to-attribute comparison to match the campaign ID in the Journey Data and Contact Data Decision Split Filter

I am not sure what I didn't wrong, but the Done button is greyed out, so I can't save the Decision Split. Greyed out Done

Have you experienced this before? What did I do incorrectly?

I refrain from doing it but I know a workaround would be linking a DE to Attribute Group keeping the campaign status and run automation on schedule.

  • 5
    Is one of your attribute to attribute field nullable? In that case, a popup states "Nullable fields cannot be compared. One of these two fields is nullable.", but allows you to save the comparison anyway, but not to create the split (greyed "Done") Aug 8, 2022 at 8:59
  • Have you tested the decision split functionality with Status equals In Progress alone? We've not found the need for your first filter criteria the campaign member ID included in the Journey entry criteria will make the link to the synched DE without it.
    – TimZ
    Aug 8, 2022 at 9:45
  • @FrançoisPerret the values aren't nullable. Id is a PK of the Campaign synchronised DE while CampaignMember:Id is also not nullable in the journey DE.
    – weliott
    Aug 8, 2022 at 11:44
  • @TimZ - yes, the split with Status alone, but Lead to Campaign is a 1-to-many relationship, hence it needs to add the first filter criteria with campaign ID. In fact, SFMC promoted a warning message at the top after I added Status in: "At least one attribute in this filter criteria could produce multiple matching values. By default, Journey Builder uses the first matching value. You can use attribute-to-attribute comparison to determine the right match."
    – weliott
    Aug 8, 2022 at 11:48
  • @FrançoisPerret, I am sorry. I have misread the DE field name and can confirmed that the CampaignMember:Campaign:Id ID is the field and was indeed a nullable value in the journey DE. I tried to updated the field to "is required" but I still get the "Nullable field cannot be compared" warning. More research showed this is an known issue - trailblazer.salesforce.com/issues_view?id=a1p3A000000KRe8QAG
    – weliott
    Aug 8, 2022 at 14:58

1 Answer 1


Attribute to Attribute comparaison should be done between non-nullable fields.

You will be able to save the comparison if not (which can be misleading), but not to activate the decision split, hence the greyed button.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .