Recherches récentes
Pas de recherche récente

Mary Thomasson
Adhésion le 15 avr. 2021
·
Dernière activité le 27 oct. 2021
Suivis
0
Abonnés
0
Activité totale
15
Votes
8
Abonnements
5
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 Mary Thomasson
Mary Thomasson a ajouté un commentaire,
Please make all columns functional as sort options and at least add 'Organization' to the tickets view. Configuration would be even better.
Afficher le commentaire · Publication le 03 juil. 2018 · Mary Thomasson
0
Abonnés
14
Votes
0
Commentaire
Mary Thomasson a ajouté un commentaire,
We need this because of the way Organizations are mapped with Accounts in Salesforce, by Account Name. If an Account Name is changed in Salesforce, a new Organization is created in ZD and all of the previous ticket history remains on the old Org. If I don't catch the change before a ticket closes on the new Org, we're stuck with it. I don't want to delete the unusable Org because it messes up reporting and makes tickets harder to find. My workaround is to re-name whichever Org has the fewest closed tickets to "DO NOT USE [Company Name]", add notes stating why the Org should not be used, move all users, tags, etc, to the correct Org, and make sure that the correct Org is hooked up with SF going forward. It's not a trivial process. If we are doing this wrong and it's possible to have the Organization name update concurrently with the Account instead of creating a new one, that will solve our problem going forward, but still leaves me with a healthy handful of "DO NOT USE" Organizations that need to be merged.
Afficher le commentaire · Publication le 24 janv. 2018 · Mary Thomasson
0
Abonnés
2
Votes
0
Commentaire