Managing Cancelable Partial Updates using MVVM

I’m new to MVVM and am trying to establish good practices as I convert a large non-Model-View WinForms project. Here’s an example of a solution I’ve implemented. I’m wondering if there is a better pattern for solving this class of problem.

MyModel has ten properties. MyView exposes two of them for users to update. MyViewModel handles the usual stuff in between.

Other models depend on MyModel’s properties, so I only want to change MyModel when values are committed to. MyViewModel has OK and Cancel buttons, so instead of having MyViewModel directly update MyModel when the user interacts with MyView, I’ve created another layer: MyTempModel. MyTempModel contains two properties which correspond to the two from MyModel.

So inside MyModel, prompting code looks something like this:

var tempModel = new TempModel{Prop1=Prop1,Prop2=Prop2};
bool? response = new MyView().ShowDialog();
if (response.HasValue && response.Value)
{
    Prop1 = tempModel.Prop1
    Prop2 = tempModel.Prop2
}

Thus if the user clicks ‘Cancel’, MyModel’s properties are not changed. Note: Not shown here is that I set a reference to MyTempModel in MyViewModel once to establish that wiring. MyViewModel subscribes to property changed events in MyTempModel and MyView uses databinding to connect to MyViewModel.

model - > view data flow summary: MyModel sets property in MyTempModel, which fires an event. MyViewModel’s evenhandler picks up the change and sets a dependency property, causing MyView to update.

view -> model data flow summary: Changes to MyView result in dependency property in MyViewModel to change. This property’s setter pushes the value to MyTempModel. When user clicks Ok then MyModel copies values from MyTempModel.

I appreciate any and all design wisdom for this pattern. I'll gladly update this info if anyone needs clarification.