Technical Latest content Contact forms Forums Blogs Resources

1760-01-01 00:00:00.000 DeletedDate value in contact table

lock
push_pin
done
Answered
2
1

Hello,

Why is the "1760-01-01 00:00:00.000" DeletedDate value used for contact (company) instead of "NULL" when a new contact is created?
In this article - Soft delete | SuperOffice Docs - it is mentioned that they are the same, but what is the difference between them?
What consequences would there be if one changes this value to "NULL"?

Laimonas Oberauskis
16 Feb 2026 | 09:43 AM

All Replies (1)

Previously the C++ code that was used for modeling the database structure didn't support/understand NULL, so 1760-01-01 = null

As you can read from the article you linked, the code supports both, so changing it to NULL in the database shouldn't matter, the question is then why would you want to do that?

David Hollegien
17 Feb 2026 | 09:55 AM
Thank you for the information.
One of the customers has some integration with JIRA and they say the companies that have the "1760-01-01 00:00:00.000" as DeletedDate value are not imported. Therefore they are wondering if they can remove those without breaking anything. I tested replacing this value with NULL on onsite and seemingly nothing happened (maybe only on the surface?). But ChatGPT says "No. Do not update all 1760 dates to NULL manually. SuperOffice logic may still rely on that sentinel value in parts of the system."
Laimonas Oberauskis
17 Feb 2026 | 11:05 AM
How are they retrieving those companies from SuperOffice? Since SuperOffice shouldn't care if it is 1760-01-01 00:00:00.000 or null in the deleted date field as value.
David Hollegien
17 Feb 2026 | 12:18 PM

Add reply