You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Create a report with "Table" output type based on JPQL query. The query must have a condition with Date parameter, e.g.:
select
e.stringField as "stringField",
e.dateField as "dateField"
from sample_MyEntity e where e.dateField >= ${dateField1}
Create a couple of entity instances. One of them should have a very old date in a date field, e.g. 01/01/0001
Run the report from the Report editor - type the 01/01/0001 value as a date parameter value
Expected behavior: the entity with the 01/01/0001 field will be in the results table
Actual behavior: the entity with the 01/01/0001 field IS NOT in the results table
The problem is that DateField transforms the date and store the date modified by the com.haulmont.cuba.core.global.DateTimeTransformations. For very old dates these transformations are probably done incorrectly.
The text was updated successfully, but these errors were encountered:
gorbunkov
changed the title
Report run dialog works incorrectly when a very old date is a report parameter
Report run dialog works incorrectly with a very old date is a report parameter
Jul 6, 2021
Environment
Description of the bug or enhancement
Create a couple of entity instances. One of them should have a very old date in a date field, e.g. 01/01/0001
Run the report from the Report editor - type the 01/01/0001 value as a date parameter value
Expected behavior: the entity with the 01/01/0001 field will be in the results table
Actual behavior: the entity with the 01/01/0001 field IS NOT in the results table
The problem is that DateField transforms the date and store the date modified by the
com.haulmont.cuba.core.global.DateTimeTransformations
. For very old dates these transformations are probably done incorrectly.The sample project: report-date-error.zip
The forum topic: https://forum.cuba-platform.com/t/pivot-table-max-data-size/14866
The text was updated successfully, but these errors were encountered: