Currently we are facing some issues that when we create empty values into the database, the value is null although we have set the default binding value to 0 in the database. Is this a normal behavior from K2 SMO create method??
Diagnoses
N/A
Resolution
This is a bug. The only workaround is to manually enter the default value you want in the input mappings, instead of leaving the input mappings blank.
