How do I change Lead conversion NOT to default to create New?

The v14 upgrade changed the default behavior of lead conversion (?) to creating a new Contact and keeping the panel closed.

This is causing behavior that promotes duplicates when name spellings are not exact or nicknames are used, and creates confusion because the "Search" option is not displayed unless you "Reset"

I would like to change the default behavior to search/create instead

Is it possible to do that within the framework?

If not, any suggestions on code customizations?

Thanks,

FrancescaS

  • Hi  ,

    I don't have a suggestion on a code customization to alter this behavior. As an alternative to code customization, Upsert Deduplicate applies any deduplication detection rules during lead conversion to alert users to potential duplicates:

    The benefit here is that this allows for a more consistent experience to identify and mitigate potential duplicates rather than depending on individual users to perform the searches to find those potential matches. 

    Let us know if you would like a more in-depth demo of our most popular plugin!

    Chris

  • hi   I don't think Sugar would change that behaviour, more likely it's a bug

  • Hi  ,

    This is an intentional design choice as indicated in step 5 of their documented steps to convert a lead. From an end user perspective, I think their objective is to reduce the number of clicks it takes to convert a lead. In practice though, Sugar's native duplicate check rules (exact match on name only) are lacking and can result in poor data quality like what Francesca is seeing.

    Chris

  •  It should do a `<module>/duplicateCheck` request automatically for both Contacts and Accounts. If it finds a result it shows you the ignore create new / select buttons, otherwise it will assume its all good and automatically have the panel closed as it requires no User input. If you have required fields in the view it will not auto close the panel however as it requires User input to be able to mark the Contact / Account as ready to be created.

    You should be able to customise this logic as its a all done within the JS and then when you press Save and Convert it sends the data off to the server to process. From memory there are a few convert / main-convert views and layouts in Leads but I haven't personally customised it to know the exact file you'd need.

    Equally you could update the duplicate check settings for Contacts which are on the $dictionary as you would have the same problem in Contacts create view directly.

  •   is right. The biggest problem we face is the limitation in the duplicate check.

    One case that came up is first and middle initial in the first name field was throwing off duplicate check, as do suffixes in the last name field.

    We have a team who cleans up leads but some fall through the cracks as Leads come from a variety of sources including Web Forms, spreadsheet uploads, and even responses to email campaigns (with all the caveats that email parsing brings).