Duplicate Search and Merge- The Perfect Data Doctor

Ken - we have completely redesigned the app using Lightning components. it takes care of state size limit issue. Would love for you to try it again. - cheers

Ken, Sorry that that View State error prevented you from using this App. Since we are using native solution to manipulate duplicate data we run into View State error intermittently. This error is encountered by some users/orgs and not all and we have not been able to replicate and fix it. We have decided to remove this app from AppExchange until we have a fix for this. thank you for giving our App a try. - Rajeev

Appreciate the positive review and thank you for sharing the feature ideas. Additional filtering criteria is on our road map. I will ping you once we are ready with those. - thanks, R

@Duncan, it is hard to take your review as legit. You seem to have spent 10 minutes with the app (based on the time stamps we have for installation to your review). Regardless of how you brilliant you are, you couldn't even have got a hang of what this product can do. Besides, trying to solve your bulk de-dupe problems in your FREE dev org that is tied to your personal id. Really? Your community profile has nothing but one review. For someone so quick with the reviews, i find it very hard to believe that your review is not staged. It seems like an intentional attempt to bad mouth a legit product that is solving a critical need. BTW, quite a few orgs are already using it. Having said that, here is our POV on your review itself: 1. While some people might like to be able to pick master records for thousands of duplicates, it will take you hours before you can run the dedupe. For certain you cant run as scheduled job. We are not attempting to solve that problem currently. You should perhaps use a standard SF DeDupe experience that lets you do that one record at a time. 2. Although, age could be one way to handle, there are other attributes that you can use to filter the master selection. While in your FREE dev org query time may not be an issue, for orgs dealings with 100s of thousands of records we need to let users pick the fields that we know are indexed. You conveniently forgot to mention about fields for filtering. 3. You do have flexibility to review and edit master records' details before merging and can unselect the records you dont want to merge. You could modify the data to make sure that masters look right and rerun the de-dupe. 4. The product has been used successfully in "real" life orgs to merge/manage thousands of records. Would be happy to work with you to develop a custom solution if you are really looking for a solution.

Thanks for your feedback Ryan. We didn't include number fields for dupe searches as we didn't see the use case for that. Based on your comments, we will add that in our next version. Also, saw your comment on view state error. Would love to get more information on how you got that so we can replicate on our end. What will make us earn a 5 star rating from you? - cheers

Thank you for the awesome review Robyn, we are happy that you liked our product. I case of any queries, issues, suggestion or feedback, please do write to us at rajeev@mirketa.com, we would love to hear more from you. Thanks again for helping us out making the product better. Cheers- Rajeev

@Ryan @ryan could you please give more details on the scenario so we can replicate this issues at our end? - thank so much.

https://success.salesforce.com/ideaView?id=08730000000aLDIAA2

I'm seeing this too. :/

Hi Rajeev, That's definitely better. Although having to scroll as much as the org. has fields for the researched object can be cumbersome. a more concise UI would help (X number of lines per row, and Y number of rows per view?) As for the master record selection, the filter can be your baseline, but ideally the user should be able to modify which record becomes the master within the search result, somehow. Ex: If we make a search by first+last name, and set the "latest updated" as master, maybe for object dependency reasons, we might want to switch master to another duplicate record within the result page.

Hi Victor, we have worked on the feature that you pointed out. No need to exit the system to compare duplicate records and modify anymore, in the new version you can now compare all your duplicates on the Modify page and can manually edit/select which field value you want from which record, that'll automatically go into the master record. Thank you for your valuable suggestions and helping us out making the product better. Do try the updated product and write to us at rajeev@mirketa.com incase of any queries or suggestions, we'll try to incorporate any/all suggestions possible to make the product better for our users...cheers - Rajeev

Thanks for the detailed review/feedback Victor. Extremely helpful in prioritizing the enhancements. 1. We will add the record id field for the report. 2. We process the duplicates within Salesforce unlike other bulk dup management apps that take the data outside SF for processing and then presenting the merged records. Since we rely on Salesforce for page size limitation, we can't change that. With the current setup you could still manage thousands of duplicate records at a time which we feel is sufficient for most organizations. 3. Since Dupe Catcher does a great job for incoming duplicate data, we don't have this very high on our priority. Do you think we need this? 4. We have enhancements plan for the merge report fields. We will include your suggestions. 5. We wanted to start with something simple on master record selection. I would love to hear your suggestions on what would be a good set for master record selection. you can send me a direct email at rajeev (at) mirketa.com. Thanks again for detailed review. it is helpful indeed. cheers