Previously, I'd mentioned an Issue with Visual Studio 2019 Community (16.9.4) that it got into the setter before instantiating the viewmodel. On the next day, I got an update so now it's 16.9.5 BUT that didn't solve the issue and I thought it's just like the xaml binding error I used to get in output window, when worked with xaml files in previous versions of my app, that doesn't throw runtime exception. And that time it caused the issue only in debug mode, I don't get that error when I run with CTRL+F5.
Now in two other views I've same problem. In the Edit Transaction view even though I've initialized the Heads in the constructor it remains null:

same with the Edit Lease view, Spaces is null:

this time it actually throws runtime exception (EDIT in release mode and run without debug with CTRL+F5) in both Edit Transaction and Lease views BUT as before it doesn't in Edit Space view:

These combobox like controls have been used in exact same way in all these three views. If I set a breakpoint in the constructor of either Transaction or Lease view and let it hit and go I don't get that exception!
The only difference between the Space view and Transaction as well as Lease view is that viewmodels for those have overridden a virtual method, setStatesOnClone, which is called in the setOnEdit method of EditBase, base class for all edit views.
EDIT
When I click the edit button, at the bottom right corner of those views, the setOnEdit is called. Tried to upload one more gif, less than 3mb, several times in between last 2 paragraphs, but I couldn't, why?
