I need to do an attribute-to-attribute comparison as part of a Decision Split (Journey Builder). One of the attributes happens to be from a Synchronized Data Extension (Sales Cloud source). Apparently one cannot compare attributes when one of the two is nullable but I am stumped on best way to set a field to non-nullable/required as I see no Edit option like one sees on typical Data Extensions. I've tried including a default value in the Sales Cloud source object but it still comes in as nullable. Any suggestions on how best to do this?

[My thoughts for a plan B include: a.) Set field as required in Sales Cloud object (I believe this will impact existing records) b.) Replicate the Synchronized Data Extension with a SQL Activity (too many moving parts!)]

  • As of Dec 2020 - this is still the case. We tried to go with the Sales Cloud Object - as required - then unsync the field in Contact Builder - and re-sync it to reflect the change, which doesn't solve it. Looking at other Synced DEs, other CRM mandatory fields also come in as nullable in Synced DEs.
    – LimeWeb
    Dec 1, 2020 at 21:20

2 Answers 2


If you don't want to update the field in Sales Cloud, your only other option as you stated is the write a SQL Query to copy that Synchronized Data Extension.

Before you do that, you do need to check if those values for the field have non-nullable/nullable values. You wouldn't be allowed to check the field as non-nullable if you have nullable values.


As far as I can see, only the PrimaryKey field in sync DE is set to non-nullable.

I recently had the exact same situation as you. We tried changing the field in CRM. When viewing the Synchronized Entity in Contact Builder [>Contact Builder > Data Sources > Synchronised > Synchronized Data Sources > {Your Synchronized Entity}] our field did come through as "Required" to synce (as opposed to "Optional"). However, in the actual Sync DE, the field was NULLABLE.

Our solution was to create a query that would update the initial Journey Audience Entry DE with a boolean field. It was this boolean field that was then used in the Decision Split activity. Make sure the entry source DE is configured in Contact Builder so you can use Contact Data.

You must log in to answer this question.

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