Pro 3.3.1 Branch Versioning Not Recognizing Attribute Value Change as Conflict

[Ed_]

So i have this enterprise layer which has a branch version that i am playing with. 

i changed a couple of the attribute values of the same attribute and row in the branch version, so that it'd be flagged as a conflict

i hit reconcile (by attribute (column)) but the i am not getting a conflict.

am i doing anything wrong here?

[DavidSolari]

Try flipping back to DEFAULT and changing the entry_note to a brand new value, does that prompt a conflict?

[Ed_]

thanks but that would be an update-update conflict where both the versions have been modified.

i on the other hand was trying to whether Pro would flag the changes made to the branch version which i guess is not possible in Pro at the moment.

The idea is for example let's say the changes you made in the branch version were not correct but the user does not actually know that and they reconcile and post the changes anyways thus updating the default version with the incorrect data. So i was wondering if there was a way to prompt changes made to existing feature attribute values so that can be reviewed before being posted, if that makes sense.