--- In [email protected], "Stephen" <sd_br...@...> wrote:
>
> I have written a program where you select a record and it is displayed due to 
> the form being bound to the value object, when I update the record it updates 
> in the database okay, but when I re-query it it crashes with the following, 
> cant seem to make head nor tail of it...
> 
> mx.data::Conflict {
>   cause = mx.data.messages::DataMessage {
>     body = [["heating_name"],
>     {
>       heating_id = 2
>       heating_name = "Radient Heat x"
>     },
>     valueObjects::View_heating {
>       heating_id = 2
>       heating_name = "Radient Heat"
>     }]
>     clientId = null
>     correlationId = ""
>     destination = "view_heatingRPCDataManager"
>     headers = {
>       newReferencedIds = null
>       prevReferencedIds = null
>     }
>     identity = {
>       heating_id = 2
>     }
>     messageId = "BEC62CE9-C4FA-4DB9-19A3-3459879B4269"
>     operation = 3
>     timestamp = 0
>     timeToLive = 0
>   }
>   causedByLocalCommit = false
>   clientObject = valueObjects::View_heating {
>     heating_id = 2
>     heating_name = "Radient Heat"
>   }
>   destination = "view_heatingRPCDataManager"
>   errorID = 0
>   message = "Local item has changes to properties that conflict with remote 
> change."
>   name = "Error"
>   originalObject = {
>     heating_id = 2
>     heating_name = "Radient Heat x"
>   }
>   propertyNames = ["heating_name"]
>   resolved = false
>   serverObject = heating_id=2
>   serverObjectDeleted = false
>   serverObjectReferencedIds = {
>   }
> }
>


Apparently this is due to loss of data management and can be corrected by going 
to Data/Services>DataType>View_heating and enabling data management of the 
valueObject on each of the CRUD service operations. Took me 5 hours to figure 
out by a process of elimination hope it saves some one some time.

Reply via email to