Af:dialog cancel problem on new VO row

Question

Using 11.1.1.4.
I have an af:popup that contains an af:dialog which itself contains enterable components mapped to VO attributes, the first being an af:selectOneChoice (body-part list). The body-part list draws from an LOV setup on the underlying VO attribute. The LOV RowSet is initialized in the model tier for the row each time the popup is invoked to ensure it contains all the values allowed.
Everything works fine except when:
a) user adds a new row to the underlying VO and invokes the popup to initialize the new row values, and
b) user selects a value out of the body-part list, and
c) user elects to Cancel the dialog
The PopupCanceledEvent fires a Delete Operation on the underlying VO in the above case, to remove the new row just added.
All this works fine, but if the dialog is now invoked either for another new row, or for an existing row, the body-part list shows the value that was selected at b) above and not the value as it is in the Model row (this has been verified). If I add and delete the row using the Delete Operation off an icon above the VO table (outside the dialog), then no issues. The problem doesn't correct itself unless / until user goes in to the dialog again and completes the add row process by hitting the dialog OK button. User can then delete this new row using the icon, and then edit and add operations all work fine again.
Everything in the model looks fine, the problem just seems to be that the UI components in the dialog aren't initializing properly from the values I know to be in the model WHEN AND ONLY WHEN the dialog has been canceled on the add of a new row (cancel of an edit doesn't cause the problem). I've tried various PPR requests to try and sync the components up with the bound values, but no luck.
Does anyone have any suggestions as to what might be going on here ?
Thanks,

Answer 1

Thanks, again that's fixed it up. Appreciate the support.
I put a ResetUtils.reset(body-part-list component) in the bean member handling the PopupCanceledEvent and it all works fine now. Don't really understand what's going on here, and why the manual reset is required for this item, but it's working ...
Thanks again,