Community Tip - Want the oppurtunity to discuss enhancements to PTC products? Join a working group! X
In the operator model data base table: PTC.SCA.SCO.Site, there is a field for timezone, where the values are actually offsets to UTC. Example, right now, for US eastern time, you'd put in -5:00 for 5 hrs behind UTC.
Is there a scheduler/thing/other entity that adjusts this when daylight savings times comes around? Example, for US eastern time, -5:00 will need to adjust to be -4:00.
Seems like there should be something that handles this if we are encouraged to store a timezone offset in the DB table. If there is not, any best practices to create this customization?
Solved! Go to Solution.
Answer: no
(had to wait until day light savings happened in the US)
You have to create your own scheduler to adjust this.
Perhaps a better solution would be for this field to be a time zone code (e.g., "EST") that is recognized by the parsedate functions that take into account daylight savings time. Timezone offset would still be helpful, but seeing as this is a standard column included it should probably come with a built in adjustment scheduler for DST
Answer: no
(had to wait until day light savings happened in the US)
You have to create your own scheduler to adjust this.
Perhaps a better solution would be for this field to be a time zone code (e.g., "EST") that is recognized by the parsedate functions that take into account daylight savings time. Timezone offset would still be helpful, but seeing as this is a standard column included it should probably come with a built in adjustment scheduler for DST