The workaround is to subscribe to the Form View Item Updating event and look for string.empty New Values and set those to null instead.
Here we have a Text Box inside an Update Panel inside the Edit Item Template.
Since two way binding is not supported for the First Name Text Box, the special code for extracting values is not generated resulting in null being sent back for the First Name property. I just don't understand why using a nested control doesn't work properly.
This Form View behavior can be problematic when we we need the original object and the modified object to perform an update with conflict detection (see LINQ to SQL example below). We're a friendly computing community, bustling with knowledgeable members to help solve your tech questions.Please join our friendly community by clicking the button below - it only takes a few seconds and is totally free. Is that because I haven't bound "m Logo" to any controls in the edit Item Template? I have a Form View control populated with some labels that use one way databinding to a database.You'll be able to ask any tech support questions, or chat with the community and help others. NET 3.5 SP1This post describes two gotchas with the Form View control when binding:1) When performing two way databinding, Null values and Nullables get changed to string. 2) Two way binding is not supported for nested controls.Note that Conflict Detection is set to Compare All Values in the Object Data Source.In brief, LINQ to SQL compares the original value and new value and generates SQL code to update the original object.event when an Update button (a button with its Command Name property set to "Update") within the control is clicked, but after the Form View control updates the record.This allows you to provide an event-handling method that performs a custom routine, such as checking the results of an update operation, whenever this event occurs.