Friday, April 19, 2013
The capability to not mark a persistent object as modified for saving if only its non-persistent properties were changed
I am not sure if this will be helpful for many XPO customers, but there is definitely a number of scenarios where you may welcome the implemented behavior. Refer to the tickets below to learn more.
http://www.devexpress.com/Support/Center/p/Q489119.aspx - implemented in 13.1 where you can use the new XpoDefault.IsObjectModifiedOnNonPersistentPropertyChange and Session.IsObjectModifiedOnNonPersistentPropertyChange properties.
http://www.devexpress.com/Support/Center/Issues/ViewIssue.aspx?issueid=S34863 - requested in the past by other customers.
Take special note that in the current version it is already possible to avoid change notifications for non-persistent properties by not using the OnChanged or SetPropertyValue methods in setters of your non-persistent properties.
OnChanged or SetPropertyValue methods in setters of your non-persistent properties.