Skip to main content

When adding a net new Boolean field to an existing object with records, when setting the Default value, it would be great to have an option to update all fields to this value.  The primary reason for this ask is due to the inability to target NULL values in a freshly created boolean field requires the admin to create a dedicated rule just to set all field values to Null prior to updating with real “true” data. 

An additional item that would support this would be to limit any Boolean field to only Two states… True/False and eliminate Null. 

This would be SO nice to have. I know about this gotcha and it still trips me up from time to time.

Been there, would be nice as a quality of life improvement to safeguard me against myself when I forget that default values don’t do anything for existing data.

I've tripped over that same stone more times than I'd like to admit.

Yup + 1 here. Have a rule that I can run ad-hoc to default them. But, why, when adding a boolean field you’re given the option to apply a default value, only to have that value not apply is truly baffling. 

 

Also, worth noting that unless using Horizon Rules (Which are a significant improvement) there’s no way to accomodate a boolean value of null via Rules Engine - it appears that its logic doesn’t consider Null to be != True, for example.

We do the rule work around too.And, this works as expected.

 

However, the main issues I have with this is,

 

  1. This doesnt work on all objects. What if it is a back end field on CTAs or SPs?
  2. I dont want my modified date update. modified could be used in rules to only fetch most recent modified records. This means all the records will be updated.
  3. The time it takes ot build the rule and wait for it to execute.
Terms & ConditionsCookie settings