Mahmoud BECHAA - 5 years ago
@Chris Soricelli : That's more less what we did, that's to say : using site field to store address data in it, with a workflow on accounts in order to update site field with address data every time the record is saved. But I find this trick very abnormal for such a CRM as Salesforce, which should offer the possibility to use cleaner solutions...
Chris Soricelli - 5 years ago
Here is what I implemented for merging. Maybe this will help others. We are on Salesforce Classic and have 266,000 company records that came from a database that has been in place for a long time, containing many duplicates, so I hope that this helps someone else:
Daniel McGarry - 5 years ago
We're planning to deliver a new merge tool in Lightning for Spring '17 (safe harbor) that lets administrators use the Search Results layout for this. In this way, the columns on the record selection screen will surface the same Account fields you’d see when using Search. Administrators can customize these fields to match the needs of your organization.
Rick Knapp - 5 years ago
I had a meeting with the SF Product Manager almost a month ago about this pain point and he assured me that he would post an update here but unfortunatly we're still waiting. Long story made short. SF is throwing all their eggs in the lightning basket and any improvements will be lightening centric. I was told that the first merge improvement will be on the Lead Object, then Contact and last but not least Accounts. (Safe Harbor and all that Jazz). All rolled out in the next 6 to 12 months but I'll let SF fill in the details. Very dissappointed but that's the roadmap that was share with me. Continue to let SF know your concerns.