Am I missing something obvious in how UpdateMulti works?

I have an entity retrieved like this:

  DrugUnitEntity newDrugValues = new DrugUnitEntity("100001");

At this point, DepotID property of the template entity is "01".

Then I update the value as a template for the save:

  newDrugValues.DepotID = null;

            DrugUnitCollection saveDrugs = new DrugUnitCollection();
            saveDrugs.UpdateMulti(newDrugValues, DrugUnitFields.ID == drugUnitIDsToUpdate);

I find that my records will not have the DepotID value updated to null in the database unless I do this instead of a direct property assignment:

   newDrugValues.Fields["DepotID"].CurrentValue = null;

What am I missing?

version info: SD.LLBLGen.Pro.DQE.SqlServer.NET20.dll: 2.6.8.1114 SD.LLBLGen.Pro.ORMSupportClasses.NET20.dll: 2.6.9.703

After setting the field to null, what's the value of:

newDrugValues.Fields["DepotID"].IsChanged

IsChanged is false after setting it to null

Setting to some other value such as "99" makes IsChanged true.

Must be that the field isn't generated as nullable. Does the field accept NULL at Database?

Ah, that's the key. Thanks!

Yes the db accepts it, but since the entity was generated from a view it didn't pick up the correct settings for nullable. Manually setting them in the designer solves it.