Trying to write zero (Integer) to Active Directory attribute using OOB sync project but failing

All AD frontend assume 0 as "default" for a non-set Integer property and so do we. But if the property is set as mandatoy by the schema we wouldn't delete it even if the "default" value 0 should be set.

Only when AD property set to mandatory, one identity can write '0' integer value to AD, else it is not possible?

If the property type in AD is Typ „String“ (Syntax = "2.5.5.4“ TypeName="ADSTYPE_CASE_IGNORE_STRING") you can alos write a 0.

But as 0 is the default value for the integers, writing a 0 to a non-mandatory integer property will lead to the removal of the property.

Thanks. It makes sense.

String was always the option but we want to understand the reason for integer failure. Thank you.

Thanks. It makes sense.

String was always the option but we want to understand the reason for integer failure. Thank you.