I'm using NPSP installed packages and the NPSP lead conversion screen.
When I convert a lead and want to associate to an existing affiliated account....does the match only consider Account Name? That is what this documentation implies:
- Affiliated Account (5): Includes these options:
- None: NPSP should not create an Affiliation between the Contact and Account.
- Affiliate with Existing: Select if the Lead's Company matches an existing Organizational Account, and you want to create an Affiliation between the Contact and Account.
- Affiliate with New Account: Select to create an Affiliation between the Contact and a new Organizational Account, created from the Lead's Company.
In my use case, the company name that gets entered in the lead Company field (via an online form) can easily vary from the existing account's name. I would prefer to fuzzy match on Company Street and Company Phone OR Company Street and Company Zip. I tried to setup a separate Duplicate/Matching Rule, but I'm not seeing any improvement. Only when the lead Company value is exactly the same as the existing account's Name does it offer the option to affiliate with an existing Account.
Has anyone had a similar requirement/need? Any suggestions for a workaround?
@Janwyn Toy not sure if you got a solution around this but if there is no OOB solution for it, one way to handle this would be to allow users to find existing accounts in SF by Account name (min. 3/4 characters to enter) on the web/online form front such that the account name comes clean into SF.
Though its an API usage overhead and external implementation work. Just throwing some ideas.
