steps to reproduce:

* go to any property that uses integer validation, click members button
* change one of the values to be "10a", click OK

expected results:

* property drill-down prevents that value, shows an error message below the singular invalid property, and doesn't allow the OK action to proceed until the user fixes the validate error

actual results:

* the drill-down screen closes
* no errors are shown
* the aggregate property doesn't change to "Member Values Differ" as one would expect if the new value had made it into the aggregate
* click members button again, notice that the "10a" value is no where to be seen, and that the previous values have been restored

-----

i think we DEFINITELY want validation at the drill-down level because without it a user made unexpected lose multiple changes to a component, and wouldn't even necessary know it until they have the fore-thought to reopen the drill-down component for that property and confirm whether their changes had gone through