Búsquedas recientes
No hay búsquedas recientes

Ruben Cortez
Incorporación 09 mar 2022
·
Última actividad 09 jun 2022
Seguimientos
0
Seguidores
0
Actividad total
16
Votos
0
Suscripciones
9
RESUMEN DE LA ACTIVIDAD
INSIGNIAS
ARTÍCULOS
PUBLICACIONES
COMENTARIOS DE LA COMUNIDAD
COMENTARIOS DE ARTÍCULOS
RESUMEN DE LA ACTIVIDAD
Última actividad de Ruben Cortez
Ruben Cortez creó una publicación,
We're using a custom field on the Organizations to capture data that's unique to each. I want to prevent an accidental copy of the same value in another organization.
SQL fields set unique come to mind.
Thanks
Publicado 09 jun 2022 · Ruben Cortez
0
Seguidores
3
Votos
2
Comentarios
Ruben Cortez hizo un comentario,
+1 for this in Explore reporting and the Organizations Notes field too.
Ver comentario · Publicado 21 abr 2022 · Ruben Cortez
0
Seguidores
0
Votos
0
Comentarios
Ruben Cortez hizo un comentario,
Dump the audit logs into a dedicated Explore dataset and call it done.
Ver comentario · Publicado 01 abr 2022 · Ruben Cortez
0
Seguidores
2
Votos
0
Comentarios
Ruben Cortez hizo un comentario,
+1 and +many more who don't know that they need this.
Ver comentario · Publicado 01 abr 2022 · Ruben Cortez
0
Seguidores
0
Votos
0
Comentarios
Ruben Cortez hizo un comentario,
Ver comentario · Publicado 28 mar 2022 · Ruben Cortez
0
Seguidores
0
Votos
0
Comentarios
Ruben Cortez hizo un comentario,
A question on this topic, for Greg Katechis or others.
Is the format of the curl command
.../api/v2/incremental/tickets/cursor.json?start_time=1636997653&include=comment_events
The comments are not exported but the parent ticket data is.
Thanks
Ver comentario · Publicado 10 mar 2022 · Ruben Cortez
0
Seguidores
0
Votos
0
Comentarios
Ruben Cortez creó una publicación,
Hi All,
I have in Explore Query 1 using the Ticket dataset and Query 2 using the Updates history dataset and both queries are Table charts.
The idea is for the user to select the row or metric on Query 1 and the dashboard uses the related Ticket ID from the selection to filter the data in Query 2, to show the update history for only 1 ticket.
Possible?
I'm currently trying the Drill In feature but the UI is somewhat of a turnoff to a few users. The initial ask was to have the Query 1 selection pivot to reveal the history of the ticket. Cool idea but not possible given my limited experience with this app.
All ideas and comments are appreciated.
Thanks
RC
Publicado 09 mar 2022 · Ruben Cortez
0
Seguidores
1
Voto
0
Comentarios