Recherches récentes
Pas de recherche récente

Ruben Cortez
Adhésion le 09 mars 2022
·
Dernière activité le 09 juin 2022
Suivis
0
Abonnés
0
Activité totale
16
Votes
0
Abonnements
9
APERÇU DES ACTIVITÉS
BADGES
ARTICLES
PUBLICATIONS
COMMENTAIRES DE LA COMMUNAUTÉ
COMMENTAIRES SUR L’ARTICLE
APERÇU DES ACTIVITÉS
Dernière activité effectuée par Ruben Cortez
Ruben Cortez a créé une publication,
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
Publication le 09 juin 2022 · Ruben Cortez
0
Abonnés
3
Votes
2
Commentaires
Ruben Cortez a ajouté un commentaire,
+1 for this in Explore reporting and the Organizations Notes field too.
Afficher le commentaire · Publication le 21 avr. 2022 · Ruben Cortez
0
Abonnés
0
Votes
0
Commentaire
Ruben Cortez a ajouté un commentaire,
Dump the audit logs into a dedicated Explore dataset and call it done.
Afficher le commentaire · Publication le 01 avr. 2022 · Ruben Cortez
0
Abonnés
2
Votes
0
Commentaire
Ruben Cortez a ajouté un commentaire,
+1 and +many more who don't know that they need this.
Afficher le commentaire · Publication le 01 avr. 2022 · Ruben Cortez
0
Abonnés
0
Votes
0
Commentaire
Ruben Cortez a ajouté un commentaire,
Afficher le commentaire · Publication le 28 mars 2022 · Ruben Cortez
0
Abonnés
0
Votes
0
Commentaire
Ruben Cortez a ajouté un commentaire,
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
Afficher le commentaire · Publication le 10 mars 2022 · Ruben Cortez
0
Abonnés
0
Votes
0
Commentaire
Ruben Cortez a créé une publication,
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
Publication le 09 mars 2022 · Ruben Cortez
0
Abonnés
1
vote
0
Commentaire