Skip to main content
spencer_engel
spencer_engel
Expert ⭐️
September 26, 2024
New Idea

Consistency with "Created Date" and "Closed Date" on Call to Action Object

Related products:CS Cockpit & Playbooks
  • September 26, 2024
  • 1 reply
  • 56 views

I was doing some reporting on CTAs today and noticed that “Closed Date” on the Call to Action object always shows the same time (in my case, 6:30 a.m. CT) no matter when the CTA is actually closed. This seems weird, considering “Created Date” is also a date/time field and works properly, resulting in things like this: 

The CTA is -15 minutes old???

I opened a ticket with support and was referred to this documentation, which says “Close Date”, “Due Date”, and “Original Due Date” must be ignored. The phrasing is weird, but essentially it means that those fields’ time component are worthless, despite being date/time fields. 

I can accept Due Date and Original Due Date being generic dates (although why have them be date/time fields then??), but Closed Date should absolutely be populated with the accurate time if Created Date is. It’s just silly otherwise. Please consider this enhancement.

    1 reply

    TMaier
    TMaier
    Helper ⭐️
    September 26, 2024

    I don’t especially mind JUST using a date for Created and Closed fields, but the issue we’re seeing here is that both fields are DateTime and one of those fields IS accurately capturing the “time” component while the other defaults over to a standard value because it’s only actually capturing Date. This would make reporting confusing, but also means that running a field-vs-field filter would be difficult and unreliable without going through a “To Date” transform - and then, why capture time at all?

     

    Timezone issues are a relevant point, but we already convert DateTime to Org and User TZ’s all the time in the UI - what’s different about this one?

      Terms & ConditionsAccessibility statement