Hello All,
I suspect this one is headed towards a support call, but has anyone else come across an issue with Resolve_Downtime in CL_Call_Logging not being correctly calculated or stored? I have a whole bunch of calls (over 50% of calls selected from a random historical point in time) where resolve_downtime is 0, even though it clearly shouldn't be if the data schema description of the column (Working minutes from logging to resolving call) is to be believed. This has totally knackered our ability to report on average resolution times.
Cheers,
Dan