Hi @ZoeChristen,
Sorry for the delay– this one was tricky to solve.
The issue here was that the determinedDate field in the Determination table’s schema was using a field format that it could not properly resolve.
I’ve resolved this on your database. You should be able to continue working with that data set!
The format was set to be purely numeric where it should be simply unformatted. Behind-the-scenes, the fields display the date format decided by the database date format configuration. To not use the ‘accessible’ date pickers determined by your browser, you can either double-click the date field to enter the date directly in that format or go to User Preferences and disable the accessible date picker.
If you disable the accessible date picker setting, you will see the format configured for your database in your date fields:
