At the moment, it is possible in a cube view to define a dimension and a value that both refer to the same field in the underlying table. This is not logical, and a cube in which a value field and a dimension field both reference the same table field results in errors when opening the cube in the Universal GUI.
My suggestion would be to implement a check constraint in the cube_field table of the model database to prevent this.