I have a python (arcpy) script that extracts data from a database table, processes it, and inserts into a feature class. It works in my development environment but not in production. I recently removed a "IS NOT NULL" constraint from the database table so now the column is allowed to accept NULL values.
I verified the constraint was removed from this table. The column is nullable. And then I checked one more time... just to be sure
Where do I look next? How do I troubleshoot this issue?
Update 1 - NULL values are okay. I'm not trying to prevent NULL from hitting the database. If a value doesn't exist for a field, I want NULL.
Update 2 - The field in the database is set to allow NULL values. I verified it again. When viewing the FC properties in the catalog, within ArcMap, the field "Allow NULL values" is set to No. I'm guessing that's the problem. Why are the two out of sync and what do I do to fix it?