{"action":"created","issue":{"url":"https://api.github.com/repos/OpenRIAServices/TestIssues/issues/31","labels_url":"https://api.github.com/repos/OpenRIAServices/TestIssues/issues/31/labels{/name}","comments_url":"https://api.github.com/repos/OpenRIAServices/TestIssues/issues/31/comments","events_url":"https://api.github.com/repos/OpenRIAServices/TestIssues/issues/31/events","html_url":"https://github.com/OpenRIAServices/TestIssues/issues/31","id":127179628,"number":31,"title":"Client only properties being wiped","user":{"login":"STAH","id":2418242,"avatar_url":"https://avatars.githubusercontent.com/u/2418242?v=3","gravatar_id":"","url":"https://api.github.com/users/STAH","html_url":"https://github.com/STAH","followers_url":"https://api.github.com/users/STAH/followers","following_url":"https://api.github.com/users/STAH/following{/other_user}","gists_url":"https://api.github.com/users/STAH/gists{/gist_id}","starred_url":"https://api.github.com/users/STAH/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/STAH/subscriptions","organizations_url":"https://api.github.com/users/STAH/orgs","repos_url":"https://api.github.com/users/STAH/repos","events_url":"https://api.github.com/users/STAH/events{/privacy}","received_events_url":"https://api.github.com/users/STAH/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/OpenRIAServices/TestIssues/labels/CodePlex","name":"CodePlex","color":"ededed"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2016-01-18T08:49:28Z","updated_at":"2016-01-18T08:49:28Z","closed_at":null,"body":"<sub>This issue was imported from [CodePlex](http://openriaservices.codeplex.com/workitem/9)</sub>\r\n\r\n**[ColinBlair](https://github.com/ColinBlair)** <sup>wrote 2013-10-03 at 20:12</sup>\r\nDuring a load or submit, an entity that has client side only properties attached to it through a partial class will have those properties wiped by the load. This is caused because the load from the server is first placed into a new entity object which is then cloned into the existing entity."},"comment":{"url":"https://api.github.com/repos/OpenRIAServices/TestIssues/issues/comments/172465518","html_url":"https://github.com/OpenRIAServices/TestIssues/issues/31#issuecomment-172465518","issue_url":"https://api.github.com/repos/OpenRIAServices/TestIssues/issues/31","id":172465518,"user":{"login":"STAH","id":2418242,"avatar_url":"https://avatars.githubusercontent.com/u/2418242?v=3","gravatar_id":"","url":"https://api.github.com/users/STAH","html_url":"https://github.com/STAH","followers_url":"https://api.github.com/users/STAH/followers","following_url":"https://api.github.com/users/STAH/following{/other_user}","gists_url":"https://api.github.com/users/STAH/gists{/gist_id}","starred_url":"https://api.github.com/users/STAH/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/STAH/subscriptions","organizations_url":"https://api.github.com/users/STAH/orgs","repos_url":"https://api.github.com/users/STAH/repos","events_url":"https://api.github.com/users/STAH/events{/privacy}","received_events_url":"https://api.github.com/users/STAH/received_events","type":"User","site_admin":false},"created_at":"2016-01-18T08:49:28Z","updated_at":"2016-01-18T08:49:28Z","body":"**[koimad](https://github.com/koimad)** <sup>wrote 2013-10-24 at 02:23</sup>\r\nThis could possibly be tip of the issue there is many facets to this issue with Entity Tracking do we Track client side property changes ? do they make the entity Dirty ? and so forth. The Extraction code clearly looks at all properties to see if they are required.  \r\n  \r\nCode could be altered to only set the MetaMember.IsDataMember if the data member attribute is applied to the property, but this would restrict monitoring client side only properties all together making the code very rigid.  \r\n  \r\nFrom a Developer that has come across this problem in the past and worked around it using a property with a getter and a method for setting it, I would prefer a simpler solution. Make the IsMergingState property on the Entity Class protected internal, this then can be used within the setter of the property to check to see if a merge is occurring or not before setting the value and raising and events required to be raised. This solution would clearly be a very quick solution, other solutions could be explored as more issues are raised about the behaviour required of client side properties in the future.  \r\n"}}