Great to hear Alice, thank you for the follow-up. I had a few thoughts for this solution long-term I wanted to share with you.
If you aren't editing versioned Feature Classes with SQL this won't play as crucial a role, but I recommend doing this clean-up effort at some point in your DBMS maintenance. Although the views you created solve the issue, they don't contain the same definition as the versioned view would have. This is low-risk if you are only editing with ArcMap or ArcGIS Pro, but it would ensure quality repositories in the geodatabase
Steps
- Delete the multi-versioned views using the SDE Command Line tools (sdetable -o delete_mv_view)
- This will remove the metadata reference and the substitute views you created above
- Create the versioned views using the Enable SQL Access tool
- This will update the naming convention to have "_evw" but it will ensure the view has the correct definition