Changes to the management of dates in the database.

As of version 25.1 and upcoming versions, changes to date and time columns will be made to improve timezone management in Monitor ERP as well as prepare for an upcoming change of database manager.

What might the date changes affect?

Updates to these versions may take longer time than usual and require more disk space, especially for large databases or if multiple databases are being updated at the same time.

Adaptations or integrations that are not covered by Monitor's Support and Update Agreement risk no longer working, or displaying incorrect dates if SQL queries are not corrected. Changes to the date and time column will not affect Monitor API or adaptations that are covered by Monitor's Support and Update Agreement.

What can be done to prevent this?

Pay attention to any update of a date and time column that is used in a created SQL query for an adaptation or integration. Changes will be published for each version, changelog for database tables.

A query function that can be used when correcting SQL has been created to facilitate the date changes.

Make sure to have extra disk space available as well as an up-to-date backup.

How do I use the query function?

The query function is available from version 24.7. The function requires two parameters, a date and a timezone.

The time zone can be configured per warehouse.

• SafeGetLocalTime(DateColumn, 'Timezone')

SELECT OrderDate FROM monitor.CustomerOrder SELECT monitor.SafeGetLocalTime(OrderDate, null) FROM monitor.CustomerOrder SELECT monitor.SafeGetLocalTime(OrderDate, 'W. Europe Standard Time') FROM monitor.CustomerOrder

What happens if null is sent as a timezone?

If null is sent as a timezone parameter to the query function, the database server's timezone will be automatically assigned.

Does the query function affect performance?

For SQL Anywhere performance is affected when the query function is applied to the "DateTime" data type. For 28 million "DateTime" dates, roughly 3 minutes are added to the response time. Other database managers are minimally affected by the query function.

What data types are used by the query function?

When can the query function be added in adaptations or integrations?

The query function will work for dates regardless of whether they have the current or updated data type. This means that the query function can be used proactively to make it easier for when the dates are updated.

What know-how and rights are needed to be able to update adaptations or integrations?

To update adaptations or integrations you need access to its SQL and know how to write SQL queries.

When can integrations or adaptations be adjusted?

Adjustments to SQL queries for adaptations and integrations can be made from version 24.7.

SQL queries for customized documents and reports can be adjusted while being used. Please note that the change is applied as soon as you save. For other adaptations and integrations, the business needs to decide whether SQL queries can be adjusted while being used.

How can we get help to update an adaptation or integration that does not have a Support and Update Agreement?

An adaptation or integration that does not have a Support and Update Agreement can be updated by our adaptations department. You can contact them on adaptation@monitor.se and enter your contact information and a description of the background and purpose of the adaptation or integration. You will then be contacted by a member of the adaptation department that has created a quote of how much it will cost to upgrade the adaptation and the price of a Support and Update Agreement for the adaptation in question. Regular delivery times apply.

How long does the update take?

The update times vary depending on several factors, such as the size of the database and the number of databases being updated. We recommend planning for the process to take longer than usual.

With this information, we hope the transition to the new version will be as smooth as possible.