Anyone getting a PropertyCopy failed on a "Double Update"?

jspurlin posted on Saturday, November 25, 2006

I was just doing some testing and I noticed that I can switch into edit mode, save an update to an item in the collection and things work fine.

But, if I do not edit another item, click the same item and make no changes, then click update instead of cancel out, I get a property copy failed error. The original value was null, and I tried both leaving the value unchanged and adding a value to it, to see if other null values would throw the same error.

I am thinking of a scenario where an update is made, you forget something, go right back to the same record and make an additional update.

I am currently unable to do this.

I would like to know if anyone else has observed this behavior.

Thank you,
jspurlin

jspurlin replied on Wednesday, December 06, 2006

I know, late nights, new framework, new paradigm (remoting), new design pattern(factory), and I ask some bad questions prematurely.

I finally discovered my issue.  I was doing an update, testing a stored procedure not code, and I was not "rebinding" the data aware control, so that any fields left blank were "null" instead of bound to an intialized instance of the property I was trying to update with the business object.

The control had lost its state.