This is not a bug, it is - popularly said - by design. The property "Selected / Not Selected" only saves a value to the database when it is checked. If not selected, the value is _not_ set to false, but to null, which leads to a lot fewer rows in the database. However, the side effect is that you cannot search for pages with a property set to "false", and for dynamic properties you will experience the exact behaviour you've explained. You cannot "unset" the value if it has been set somewhere above in the hierarchy. The solution is to write your own property type which has these three options: * True * False * Null / Not Set ("Inherit" would be a good name if only used for dynamic properties) You then need to save this as an int. /Steve

Thanks Steve /Vlada

You're right that it's by design, but it is also correct to say it's a bug.  It is a bug in the design.  The property is "selected/not selected", not "has been selected at least once".

Depends on which hair you're splitting. But I'll agree that it depends on the viewpoint. It was designed this way intentionally, hence "by design". I agree that it might not be intuitive from the UI point of view, and the whole concept of dynamic properties, and the checkbox for overwriting any decendant values is inherently non-intuitive.

I guess we'll have to agree to disagree, and luckily Vladimir solved his problem.

/Steve