This is likely because I don't fully understand how the concurrency handler works, but I'm having trouble with two issues related to concurrency:
1. I have a table that has several date fields in it. These fields can all be NULL, because the dates can be NOT set. I have a SetDefaultValues handlers that provides my NULL replacement date for them. All is fine...until I have a concurrency conflict (I'm using row version concurrency). If one of the conflicting fields is a date and one of the values of that field is NULL, I get a type conversion error. How do I handle NULLs in this case?
2. Same form (hitting same table) also has a couple of custom properties defined. These properties get their data from some extra columns that might be available when the BO is filled. I check if the column exists before attempting to get the value and if the data table doesn't have the column, I return a default. This works great. However, with concurrency again, when there is a conflict, I'm getting an error that one of these custom fields isn't in "Table1" (default table name of a table in a data set I assume). Apparently, the concurrency handler is accessing this custom field, but not using my custom getter, somehow going directly to the data table. Any ideas on how to handle this better (
er...at all)?
I'm trying to release this into production, so this is fairly urgent!
Thanks!