Vor Kurzem aufgerufene Suchen
Keine vor kurzem aufgerufene Suchen

Mary Thomasson
Beigetreten 15. Apr. 2021
·
Letzte Aktivität 27. Okt. 2021
Folge ich
0
Follower
0
Gesamtaktivitäten
15
Stimmen
8
Abonnements
5
AKTIVITÄTSÜBERSICHT
BADGES
BEITRÄGE
POSTS
COMMUNITY-KOMMENTARE
BEITRAGSKOMMENTARE
AKTIVITÄTSÜBERSICHT
Neueste Aktivität von Mary Thomasson
Mary Thomasson hat einen Kommentar hinterlassen
Please make all columns functional as sort options and at least add 'Organization' to the tickets view. Configuration would be even better.
Kommentar anzeigen · Gepostet 03. Juli 2018 · Mary Thomasson
0
Follower
14
Stimmen
0
Kommentare
Mary Thomasson hat einen Kommentar hinterlassen
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.
Kommentar anzeigen · Gepostet 24. Jan. 2018 · Mary Thomasson
0
Follower
2
Stimmen
0
Kommentare