@EmilyGeo it looks like it is when I import the csv to a geodatabase table. The csv has nulls and the gdb table has the default value in the field. But I thought I set up my script to allow for nulls in the fields.
How I set up the table fields:
Solved! Go to Solution.
@EmilyGeo Hi! So I did figure out a solution, for me. I just need to recalculate the fields to be null after I import it to the database. Once they are calculated to null, it persists through the process to AGOL so I now have empty values instead of 12/30/1899 which is what I wanted. Just a couple extra lines of code, not sure if it was the most efficient way, but it works! Thanks for your help!
Hi @OliviaE,
I think you need to ensure that the new Date fields support Null values when you add them.
Moving this discussion to the Python Community for now...
@EmilyGeo Hi! So I did figure out a solution, for me. I just need to recalculate the fields to be null after I import it to the database. Once they are calculated to null, it persists through the process to AGOL so I now have empty values instead of 12/30/1899 which is what I wanted. Just a couple extra lines of code, not sure if it was the most efficient way, but it works! Thanks for your help!