Problem Note 56912: Date and datetime values are converted incorrectly in SASĀ® Visual Scenario Designer
SAS Visual Scenario Designer does not convert date or date time values correctly. Conversions might use the timezone offset for the time that is being converted. However, the timezone offset for the current time is used instead.
Example
You have a datetime that represents Jan 1, 2015 08:00:00 for a window that you created in January. You are in the Americas/New_York timezone. In June, Jan 1, 2015, 07:00:00 is displayed in the window's preview data. This time is displayed because in June, New York is in Daylight Saving Time, which is -5 hours offset from GMT. Instead, what should be used is Jan 1, 2015 08:00:00, the -4 hours offset from GMT. The -4 hours offset is what is in effect at that time of year.
This issue is not limited to just the Americas/New_York timezone. The issue could occur with any timezone, or with Daylight Saving Time changes.
There are no errors or warnings to indicate a problem.
There is no workaround.
Click the Hot Fix tab in this note to access the hot fix for this issue.
After applying the hot fix, review these items:
- all windows, scenarios, and deployments to verify that the dates and times are correct. If they are not correct, then reset those values to the proper values.
- imported windows and deployments. If you exported a window or deployment before applying the hot fix, then check any datetime values that you entered for the window, scenario or deployments.
- the window's anchor start and end date/datetime for rolling windows.
- any window input-filters that have a condition that compares date or datetime.
- any column properties that have a condition that checks against a date or datetime.
- scenario conditions that reference or compare date or datetime.
- deployments that have conditions for date or datetime.
Operating System and Release Information
SAS System | SAS Visual Scenario Designer | Linux for x64 | 6.3 | 6.3_M1 | | 9.4 TS1M3 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Type: | Problem Note |
Priority: | high |
Date Modified: | 2015-12-11 12:22:56 |
Date Created: | 2015-10-26 09:56:37 |