Yeah, I wondered if the null / 0 thing would cause statistical problems.
Even though you won't be working with fractional values, setting the field type to a decimal / double would allow nulls. Also, it's not surprising that the update process is giving you problems. I've also had issues with null integers during updates, and I believe it's got something to do with one of the backend processes that you unfortunately don't have any access to change.
The lack of spatial information in the spreadsheet could be part of it. Are you using the spreadsheet to update a spatial layer?
I'd suggest looking into alternate means of updating your features. Is this spreadsheet the extent of it, or do you anticipate having a large number of rows or frequent updates? It may simply be easier to edit the table by hand if it's small and infrequent.
If you want it automated, the Python API can edit your features in place, even when the source data doesn't have spatial attributes.
- Josh Carlson
Kendall County GIS