Why the first reply time(hrs) gets overvalued when adding a date calculated field to the query? | Community
Skip to main content

Why the first reply time(hrs) gets overvalued when adding a date calculated field to the query?

  • December 9, 2022
  • 0 replies
  • 0 views

Hello there, 

I noticed something that seems really weird for me regarding the first reply time(hrs). When I add a calculated attribute (DS Outbound Call Timestamp) to the query it gets overavlued.. The attribute was calculated as : DATE_ADD(DATE([DS Outbound call time]),"hour",1)  where the  [DS Outbound call time] is a text custom field added by our technology team on the ticket event to be able to catch the time when an outbound call took place in UTC timezone, and I needed to concert that field to a timestamp and then add one hour to be matching the Rome/Europe timezone we see always on our zendesk tickets.

When displaying that field in the query (see screenshoot 1), the First reply time(hrs) gets overvalued while the one in mins remains at it's supposed to be. The issue seems to be with the date_add founction (with "hour") but I can't understand why.

The normal situation without displaying the calculated field is the following: 

Do you have any explanations please for why explore is behaving like this? Anything wrong I've done from my side?

Thanks, 

Sahar.