SuperOffice CRM Professionals

Pretty sure you need a groupby clause here?  'GroupBy(columnName):Footer' ( docs )  

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?

The email_item table is used by the internal inbox functionality, it contains the emails that are directly taken from a specific users inbox, not only the one's an user archived in SuperOffice. Because of that, this table is indeed protected from searching (and propably because it can be a very large table). SuperOffice does not store the content of archived emails/documents in the database, but in the external document archive, which in Online can be either Azure blob storage or Microsoft 365 sharepoint. It isn't possible to query this storage directly to get the email body's.

See this pilot program forum: https://community.superoffice.com/en/forums/pilot-program/replication/

It's a bug in the API we use to retrieve the status of, or create, consultant access. The issue occurs for customers where your SuperID user was previously created as a regular user with admin rights. The API does not verify whether you still have an active user plan; it simply returns false, meaning: “You are already an administrator in this database and cannot request consultant access." As soon as the bug is fixed in the API, the button will appear.