Latest version of our Sugar Dedupit are 5.1.0 and it's work on SugarCrm 10 and above you can check your version in Module loader open browser search (cmd+f for mac and ctrl+f for Windows) and type DeDupit
You have Upgrade part explained in documentation, if you want to save current configuration check Do Not Remove Tables when you uninstall older version and after that just install new version of module .
we have verified this morning usage of DeDupit on latest Sugar 11 OnDemand and it works as expected without any issues. The explanation given by SugarCRM doesn't really tell us anything to help you diagnose the issue or understand if there is a conflict. Can you please provide us the reference ticket ID with SugarCRM that you have opened?
What i believe happened is SugarCRM didn't properly disable the module which caused an issue after uninstalling.
I would advise that you install the DeDupit release and uninstall afterwards. This should remove any traces of the module.
Do be aware that you might have other customizations that are poorly done and that our module just uncovered the issue.
We are here to help and jump on a meeting to help you resolve the issue. Since we are SugarCRM partners as well, please provide us ticket details and have them include us on resolving the issue so that we can provide all the necessary assistance and understand if it really is DeDupit that caused the issue.
The best way forward is to contact us directly, i will send you an email.
the latest version of DeDupit is 5.0.5 and it's available on SugarOutfitters. I believe that you can always download the latest version of any bought module from your profile. If that's not the case please let us know and we will send you the package directly. Your old license key will work on new version.
Please be aware that information about detected duplicates, processes and merging history might be lost after you install the new version (already merged duplicates will remain merged, of course). We advise you to read the new module's documentation before using it as it works differently comparing to the older versions.
If you have any additional questions do not hesitate to contact us.
Hello, thank you for showing interest in our module!
if you used 'Send Code to User' action and then 'Reset 2FA Secret Code', you left that user in the mode that expects email-sent code. In that case you'd need to send email once more and use the code received in the email. 'Send Code to User' always takes precedence, if you used this option you need to enter the code received via email. And, as I said, you reset the code in the meantime you'd need to send another email and log in using the received code.