How the database handles clock changes
The data on the portal is displayed in local “clock” time. This is how most suppliers would use the data for time of day charging.
This would mean that you should see a gap for Sunday morning in April, as the local clock skipped an hour. You would also see a doubled up period in October.
The data is actually stored in UTC at the database level with the local offset stored alongside, so we can report on this, when we display it on the portal we use the time adjusted to the sites local time.
Trying to explain this can be tricky, as people often turn things round in their heads, so you will need to be clear on this when advising the client.
Related Articles
Bill Val: "Null value is eliminated by an aggregate or other SET operation."
This message is just a warning from the database. The file will have processed - you will see it in the Validate tab - but the message prevents the system from marking the file as 'processed'. The warning essentially means that there are charges on ...
Changing your password
Everyone is able to change their passwords themselves in one of 3 main ways, depending on your location: Follow method 1 if you're in the office Follow method 2 if you're working remotely and have access to the remote server Follow method 3 if you ...