Master data: temporary values ​​of a dirty object

Question

I use temporary values ​​to provide some data in my application. The trouble is that as soon as these values ​​are calculated, it manages my managed objects, reporting the need for re-saving.

In any case, to prevent the change of transient values ​​when marking an object as dirty, if there are no actual changes in the object graph.

Thank,

Answer 1

Mark this amazing transient property entry in the master data. This explains things a lot better than I can in this short space, plus I'm still pondering it!

This guy recommends using the IsValid and Ivapshot flag to solve this problem, I think.

Answer 2

Could you declare fields as unmanaged properties in your data model class (i.e., they are defined in the source code but not included in the data model)?