Service Portal <sn-time-ago"/> element - how to show date+time instead of time difference?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-30-2023 04:20 AM
Hello, I am working with clone of OOTB "my-requests-v2" widget and one of the columns is "Updated". It is showing time difference between now and "updated" date. I want to show instead of this just a time and date of last update. As I see there is used element like this:
<sn-time-ago timestamp="::item.updated_on"/>
Does anyone know if there is a simple solution to change it or do I need change the logic very hard?
Kind Regards,
Adam
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-30-2023 05:25 AM
You might find this workaround on below article useful.
The Date/Time TimeAgo format preference does not affect Service Portal
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-23-2023 01:00 PM
Hi @Adam Boroch - we have the exact same issue, we would also like to change the time ago to the actual time stamp on this updated column on the My Requests v2 widget. We have followed the link @Muhammad Khan shared and other community posts/support docs however still no luck.
Did you manage to find a solution to this? If so do you mind sharing it with me please?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-23-2023 01:18 PM
Hi @Daniel R2 , @Adam Boroch
This solution requires customizing the widget: (Clone widget preferred)
Replace <sn-time-ago timestamp="::item.updated_on"/> by {{::item.updated_on}} in the html
Help others to find a correct solution by marking the appropriate response as accepted solution and helpful.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-08-2024 03:38 PM
Maybe in recent Version of this Widget, its not working by changing the code line as above (I can see the lines in 62 and 144). There is also another error which is seen, however has a KB Article KB1641841 to solve, but is very recently updated (Nov 6, 2024)
Any lead on this issue would be helpful.