Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0032569Openbravo ERPA. Platformpublic2016-04-01 09:282016-04-01 11:23
ReporterJONHM 
Assigned Toplatform 
PriorityhighSeveritymajorReproducibilityalways
StatusclosedResolutionno change required 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customer
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0032569: Wrong data in csv file exported on different time zone
DescriptionWrong data in csv file exported on different time zone filtering by a date range, like "Creation date"
Steps To ReproduceWatch the video attached below
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
has duplicate defect 0030605 closed alekosmp86 Problem with timezones at exporting CSV 
Attached Files? error_csv_timezone.mp4 (2,882,282) 2016-04-01 09:28
https://issues.openbravo.com/file_download.php?file_id=9234&type=bug
Issue History
Date ModifiedUsernameFieldChange
2016-04-01 09:28JONHMNew Issue
2016-04-01 09:28JONHMAssigned To => platform
2016-04-01 09:28JONHMFile Added: error_csv_timezone.mp4
2016-04-01 09:28JONHMModules => Core
2016-04-01 09:28JONHMResolution time => 1462312800
2016-04-01 09:28JONHMTriggers an Emergency Pack => No
2016-04-01 10:09alostaleTarget Version3.0PR16Q2 =>
2016-04-01 11:23alostaleNote Added: 0085382
2016-04-01 11:23alostaleStatusnew => closed
2016-04-01 11:23alostaleResolutionopen => no change required
2016-04-01 11:25alostaleRelationship addedhas duplicate 0030605

Notes
(0085382)
alostale   
2016-04-01 11:23   
CSV files are generated in server side, date conversions are performed regarding two possible scenarios:

* By default, conversions are done based on current client UTC offset. This is done in this way because not all supported browser versions are able to get local timezone. This transformation is known to be problematic in case of exported row being created within a different DST than current's one.
* If "Local Timezone ID" is set conversion is done accordingly, taking into account also DST changes.