Finally! This option ensures that a date is always output correctly—regardless of the timezone in which a record is accessed.
The enable timezone-independent date option refers only to the datefield. The option's available as of version 3.6.0.
If you use Ninox in the cloud together with other collaborators who are located in different timezones, you may be affected by an issue that can occur when saving a date, e.g., birthday or invoice date:
The value displayed in a date field may differ by 1 day from the entered date.
That is because Ninox stores dates as timestamps. Therefore, depending on the timezone in which you access a database, there is a possibility that a different date is displayed.
The displayed date may also be affected by Daylight Saving Time (DST).
If you work on Ninox databases across different timezones and have implemented a workaround for this issue, please follow our guidelines below before you switch over your databases.
Why is the switch not automatic?
Shortly, you won't need to make any custom adjustments, as date values will automatically be savedcorrectly. If you experienced issues with the date display in the past, we now offer the option to switch your databases.
Given the large number of databases that already exist, we require a transition period so that users have sufficient time to test and apply this new option to existing databases.
Convert existing databases
If you have been using workarounds to deal with the date issue, please keep the following in mind when making the switch:
We recommend that you manually back up your databases before switching them over.
Afterwards, check the behavior when you enable the option and adjust your scripts as needed.
How it works
The option is enabled at the database level. If you have multiple databases, perform the following steps for each database.
Open your Ninox Public Cloudin the browser (i.e. the web app; also for Apple users: not in the Mac app, as certain functions aren't available there). Then proceed as follows:
A popup appears pointing to this help page and reminding you to perform a manual backup. When you are ready, click Enable.
Still under Options, click the button Rebuild indexes.
If you also use Ninox on a mobiledevice or via the Macapp, please resynchronize your databases on at least one mobile device (refer to Synchronize content in apps). For now one mobile device will be sufficient as subsequent syncs are faster afterwards). If not, you are...
Done! Check your database entries to ensure they are correct.
First click the button to enable timezone-independent date (Step 3)
Then rebuild indexes (Step 5)
Synchronize content in apps
If you use mobile devices, you need to "transfer" the timezone-independent date entry to your native apps.
To do so, please synchronize your databases on each mobile device, as well as the Mac app, with the Ninox server.
Tap and hold the database icon (mobile device) or click the database icon (Mac app).
A popup opens. Select Reset synchronization.
Your data is synchronized with the Ninox server.
If needed, inform your colleagues using mobiles devices about enabling the timezone-independent date and advise they reset synchronization of databases on their mobile devices.
Via Reset synchronization you retrieve the current state of your database from the cloud
Values entered in a date field are now always displayed correctly, no matter from where you access the database.
For date entries outside the UTC -11:00 and UTC +11:00 timezones, e.g., on the Line Islands of Kiribati, Baker Island, Howland Island, or the Marshall Islands, the international date line may still cause date values to be saved incorrectly.
Only around the international date line, there may still be issues correctly displaying date entries
New date format will be the default
Starting with Ninox version 3.6, in each newly created database, a date value is automatically stored independent of timezone.
From Ninox version 3.6 onwards, a date—in a date field—is automatically stored independentoftimezone in a newly created database.