Timer fields do not display the correct data in Service Portal - Known Error

Timer fields do not display the correct data in Service Portal Description Timer fields, such as time worked, do not display properly on the Service Portal. Instead of showing the time worked, it will display a value such as: 1969-12-31T16:10:24.

Note that this value also differs from what is shown in the xml for the record. If you show the record XML in the platform UI, the value will appear similar to the following:

1970-01-01 01:16:10

Example of Timer field in the backend/platform UI

Example of Timer field in the service portal UI

Steps to Reproduce

1) Edit any existing incident and add the "time worked" field. This field is a timer field type. 2) Create a new incident, ensure the time worked field has information. Save the record. 3) Observe the time worked field in the platform/backend ui 4) See the same record in ServicePortal, for example: .service-now.com/sp?id=form&sys_id= &table=incident 5) Observe the data displayed (example: 1969-12-31T17:16:10)

Expected behavior Same value should be displayed in Service Portal.

Actual behavior Different value for the same field is displayed in Service Portal.

Workaround You can create or edit a new view for the incident form in the platform UI. Ensure this view does not contain the Time Worked field. Then create an advanced view rule which forces this view if a service portal URL is detected.

This issue is under review. To receive notifications when more information is available, subscribe to this Known Error article by clicking the Subscribe button at the top right of the article. If you are able to upgrade, review the Fixed In field to determine whether any versions have a permanent fix.