What is best practice for a scenario where you may have an object, that may have a different parent object depending on the form it is used in? For example, I have an object called parts. Parts can be called in my application to create a proposal (kind of sales order) of which I presently have 4 different types, they may also be used in invoicing, they may also be used in Jobs, where again parts may be used for maintenance purposes.
thanks in advance
Geoff Hirst
If you do want to update the UI, however, you can use the NavigateToPrimaryKey, which will fire the Navigated event upon completion .