Follows up on RHDM-1153.

When user creates a Test Scenario for DMN model and then adds constraint to an existing DMN Data Type property, the Test Scenario presents and error during opening complaining about incompatible type.

1. It mentions still the property field (e.g. Speed Limit) instead of the real implementing type (number with constraints).
2. To fix the Test Scenario the column needs to be redefined by selecting the property again.

Even if some error is expected in such a case (adding constraint to an existing type), the error should inform the user better. But since the base type matches, it should not force the user to remove the column and add again, it should fail only when evaluated and the values not aligned with the constraint - ie at least when re-selecting the Data Object property in Test Tools the dialog should allow to "Preserve the values" when the type base is still the same.