Vor Kurzem aufgerufene Suchen
Keine vor kurzem aufgerufene Suchen

Chris Gould
Beigetreten 16. Okt. 2021
·
Letzte Aktivität 14. Dez. 2021
Folge ich
0
Follower
0
Gesamtaktivitäten
21
Stimmen
7
Abonnements
6
AKTIVITÄTSÜBERSICHT
BADGES
BEITRÄGE
POSTS
COMMUNITY-KOMMENTARE
BEITRAGSKOMMENTARE
AKTIVITÄTSÜBERSICHT
Neueste Aktivität von Chris Gould
Chris Gould hat einen Kommentar hinterlassen
+1 - I've just spent ages trying to understand why the field isn't visible to me. "Is this an explore issue or an agent issue"? Would be good to see it, regardless of whether data exists or not.
Kommentar anzeigen · Gepostet 14. Dez. 2021 · Chris Gould
0
Follower
2
Stimmen
0
Kommentare
Chris Gould hat einen Kommentar hinterlassen
Hi @...S O'Callaghan,Yes the formula definitely works, however, I need to function as a date. Not just a normal attribute field.
So I would like to apply ranges to it like you might with ticket created-date and ticket solved - date.
For example: show me the "New attribute" for This month
Kommentar anzeigen · Gepostet 29. Sept. 2021 · Chris Gould
0
Follower
0
Stimmen
0
Kommentare
Chris Gould hat einen Post erstellt
Hi everyone,
I'm hoping this is a obvious/simple solution.
I am trying to do some rough forecasting which looks at a date 90 days after the ticket is solved. I'd like the attribute to behave like a date attribute where I can apply ranges or ideally even split into weeks and months, however, I know the latter requires extra work.
Here is my code so far and I'm stumped as to why it's not appearing as a date.
DATE(DATE_FORMAT(DATE_ADD([Ticket solved - Date], "day", 90), "yyyy-MM-dd"))
Gepostet 28. Sept. 2021 · Chris Gould
1
Follower
2
Stimmen
3
Kommentare
Chris Gould hat einen Kommentar hinterlassen
Hi @... - just wondering if there has been any changes in regards to reporting on SMS messaging in explore?
Kommentar anzeigen · Gepostet 20. Sept. 2021 · Chris Gould
0
Follower
0
Stimmen
0
Kommentare
Chris Gould hat einen Kommentar hinterlassen
We just used DATE_FIRST_FIX function to find the time the first call was made against a ticket ID, given a ticket can have multiple calls, DATE_FIRST_FIX was ideal.
We were able to nest this into a DATE_DIFF to find the length in time between the ticket creation and the first call. You can then aggregate any way you like as there is only one value provided per ticket ID.
DATE_DIFF(DATE_FIRST_FIX([Call - Timestamp], [Ticket ID]), [Ticket created - Timestamp], “nb_of_minutes”)
Kommentar anzeigen · Gepostet 13. Aug. 2021 · Chris Gould
0
Follower
0
Stimmen
0
Kommentare
Chris Gould hat einen Kommentar hinterlassen
@...,
I have been told by my ZD account manager that it's likely a Q4 (US FY) release.
Kommentar anzeigen · Gepostet 08. Juli 2021 · Chris Gould
0
Follower
0
Stimmen
0
Kommentare
Chris Gould hat einen Kommentar hinterlassen
How is this not a feature? I hope it has changed since this was posted.
Kommentar anzeigen · Gepostet 24. Juni 2021 · Chris Gould
0
Follower
1
Stimme
0
Kommentare
Chris Gould hat einen Kommentar hinterlassen
Hi - is this still on track for delivery in H2 2021?
Kommentar anzeigen · Gepostet 17. Juni 2021 · Chris Gould
0
Follower
0
Stimmen
0
Kommentare