It is possible to use advanced date queries in views and entities as described here. However, these date queries only make sense when they are evaluated dynamically: in the current solution, the date queries are stored as a static date that is determined during the database synchronisation (typically as a part of the installation of a release).

It would be good if this behaviour was changed to use dynamic dates instead, based on the current datetime (and the timezone).

An example of a view that is defined as "all invoices with an invoice date in the future":

In the current solution, the view looks like this:

select INVOICEDATE from CUSTINVOICETABLE

  where INVOICEDATE > '2022-08-17 06:35:15'

With a dynamic date determination, it could look like this:

select INVOICEDATE from CUSTINVOICETABLE

  where INVOICEDATE > SYSDATETIME()

Thus, the change should take place in the database synchronisation, where the views/entities are created.