Essential solution to help you keep your SugarCRM data in perfect shape!
Primary source of problems with your SugarCRM data is duplicate entries that you are making while working. Eliminate those with advanced detection techniques and resolve them in few easy steps.
#4092 - View all duplicates & dashlet in other modules
Hi,
Through the instruction video it only displays duplicates in each individual contact record (that's related to that particular record) rather than being able to search through all of the records and listing all of them at once. I have two questions: - Can I add the De-dupit dashlet in the main contacts module or any other module? - Can I view all duplicates found by De-dupit in a list, or can I only view a duplicate if I'm viewing a particular record? - Are there any other options for how auto-merge works? Can I select an additional option on top of created/modified date and whether the record is new/old? We have statuses where we want to keep the newest record status but when merging with older records we'd like to ensure that it keeps the older created date. - Do all fields get overwritten in auto-merge if the same field is filled in on both/all duplicate records or will it prompt that there might be a conflict? We have at least one field where it gives you options 1, 2, 3 for the same question and if it's merging and option 1 is filled in on the original and other records it should be filling in option 2 and 3 rather than writing over option 1. Is this something de-dupit will pick up or will it automatically override the other record?
Thanks, Karen
4 years ago
Hi Karen,
Thank you for your interest in our product!
Here are the answers in the same order as the questions for them: 1. Unfortunately you are not able to add the dashlet to the list view on the module where you want to detect duplicates, for now it is only available on the record view. 2. At the moment only way to preview duplicates is by using the "DeDupit Found Duplicates" dashlet on the record view and this dashlet only displays duplicates for the current record. 3. Auto merger can only be configured to decide which is original record by "Date Created" or "Date Modified" fields. Currently we are not supporting configuring any additional fields for the Auto-merger config but it might get added in one of the future updates. 4. When auto merge starts processing the original record and duplicate it will only use field value from duplicate if original one has that same field empty, otherwise we will use the value from the original. Auto-merge process is running in the background of you sugar instance and there is no way to interact with it while it is processing the duplicates, once configured to run it will merge duplicates in the background, to see which record's duplicates got auto merged you can use "DeDupit Auto Merged Duplicates History" dashlet located on the record view of any Sugar module. Essentially Auto-merger feature is supposed to be used on modules where it is easy to distinguish original record from duplicates and remove unnecessary hassle from user to manually decide which one is the duplicate, otherwise we will need to do it manually using "DeDupit Found Duplicates" dashlet.
If you have any further questions please let us know!
Thanks!
4 years ago
Thanks for responding. With the records merging, will it keep a history of all records after the merge or will it replace and delete whatever is deemed a duplicate? We'd like to: - keep the original date of the record for reporting purposes as we report on lead numbers and conversions monthly - keep latest statuses (other fields other than dates) when merging
From what we're aiming to do, does it sound like we won't be able to do this with de-dupit in its current form?
Thanks
4 years ago
Hello Karen,
When two or more records are merged duplicates will get deleted and original record will get updated with missing data that existed on duplicates or with whatever user picked when merging them manually. When merged manually there is no way to see the history of the merge, but when records are merged by auto-merge process then we can see it in "DeDupit Auto Merged Duplicates History" dashlet where you can even preview the record that got deleted in the process. Just keep in mind that this preview will only be available until the record has been removed from the database completely, that is because all record that get deleted are first "soft deleted" in database and then after some time passes by Sugar will remove them completely.
-_ keep the original date of the record for reporting purposes as we report on lead numbers and conversions monthly_ Since original record is not being deleted when merging then it should contain its date fields intact, on the other side the duplicates will get removed from Sugar and you are not going to be able to run report on them.
-_ keep latest statuses (other fields other than dates) when merging_ When running auto-merge you won't be able to control merging of the statuses based on their hierarchy, instead the status on the original record will only get updated if it is empty and duplicate contains it. Merging duplicates manually will allow the user to decide which status to preserve.
Based on details from our conversation I think it would be possible to use the DeDupit module on your Sugar but merging records would require a lot of manual work with the current version of module. In this scenario we usually offer our customers an opportunity to tailor our modules to better suit their needs, if you are interested we could discuss it on the call.
Our office is located in Europe (GMT+2) and our working hours are from 9AM to 6PM.
Thanks!
4 years ago
Hi, thanks for your reply. I'll contact the office to schedule a call.