Windows-10 Client
Windows-Server 2016
WinCC-OA 3.16 p20
Table property 'Empty if zero' doesn't work in EST US & Canada Timezone,
To elaborate more on this if we run the WinCC OA project in Indian Standard Time(IST) & Central European time(CET) , with above settings in place for table then time column with empty values displays nothing after table gets render on UI , which is correct behaviour.
If we run same project in Eastern Time (EST US & Canada) then time column displays a default date i.e. 1-Jan-1970 for empty value assigned, which is inconsistent behaviour.
Is there possibly a settings which we've forgotten to set when running in different Timezone or do we face a bug?
Thanks in advance,
Best regards,
Michel Eijgermans.
Table property 'Empty if zero' doesn't work in EST US & Canada Timezone
Search
-
- Posts: 46
- Joined: Mon Aug 08, 2011 11:50 am
Re: Table property 'Empty if zero' doesn't work in EST US & Canada Timezone
I have tested it in 3.17 with a simple test panel and I cannot see the problem.
Which datatype have you chosen for the column where trhe option "Empty if zero" is set?
Best Regards
Leopold Knipp
Senior Support Specialist
Which datatype have you chosen for the column where trhe option "Empty if zero" is set?
Best Regards
Leopold Knipp
Senior Support Specialist
-
- Posts: 46
- Joined: Mon Aug 08, 2011 11:50 am
Re: Table property 'Empty if zero' doesn't work in EST US & Canada Timezone
Hello Leopold,
Where using the following formatting:
Datatype of the content were writing to a cell 'time' via a dyn_dyn_anytype construction to directly apply color to the content.
The column in the table is formatted as:
Datatype: Time
Format: Custom -> %d-%b-%Y %H:%M:%S
H.Allign: Left
V.Allign: Object Default
Options: Empty If Zero
if the time-setting has a positive offset on UTC thus UTC+1 and further. All seems to work fine
If we apply a timezone UTC-1 and further the Option: Empty If Zero doesn't work anymore.
Could it be that a Negative offset on UTC give internally a 1969 year?
With simply changing Timezone and restarting of UI the effect is reproducible in our environment.
Maybe needles to say, but our test-environment is 3.16, we cannot test this yet on a 3.17 environment.
Where using the following formatting:
Datatype of the content were writing to a cell 'time' via a dyn_dyn_anytype construction to directly apply color to the content.
The column in the table is formatted as:
Datatype: Time
Format: Custom -> %d-%b-%Y %H:%M:%S
H.Allign: Left
V.Allign: Object Default
Options: Empty If Zero
if the time-setting has a positive offset on UTC thus UTC+1 and further. All seems to work fine
If we apply a timezone UTC-1 and further the Option: Empty If Zero doesn't work anymore.
Could it be that a Negative offset on UTC give internally a 1969 year?
With simply changing Timezone and restarting of UI the effect is reproducible in our environment.
Maybe needles to say, but our test-environment is 3.16, we cannot test this yet on a 3.17 environment.