#Convert Lead1 discussing

For me this case is even more weird there is a  multi select picklist list field called " Brand__c" in account layout however this field doesn't even exist in opportunity/lead/contact object and i am still getting an error saying "The lead conversion failed because the value for the field Brand__c is invalid. The value comes from the lead field that's mapped to the field Brand__c. Ask your admin to check the field mappings." I checked the mappings and there is no such field mapping that can be found in the lead mapping. What could be the issue please help. #Trailhead Challenges#leadconversion #Convert Lead #Flow #Custom Buttons #Multi-picklist Field #TrailblazerCommunity

You're awesome @Dodi Friedenberg! Of course, I've known that since 2017 at JVS!

A couple notes:

1. Users must also have R/E to the Title field. Since we don't use that, I hadn't previously granted access. But thanks to your Github link, I figured it out.
2. Users must have CR access to Opportunities in order for both the Opportunity Name field and the Do not create a new Opportunity upon conversion checkbox field on the conversion page to appear (Opportunity Account appears either way). Previously, those fields appeared regardless of the permissions. However, the conversion will still work without those permissions or the fields being visible. This is fine, as long as the NPSP Setting for Leads is set to the appropriate default. In my case, that's unchecked, which causes the Do not create a new Opportunity upon conversion checkbox field to be checked by default. Since we don't use Opportunities for Leads, it works out just fine that users suddenly don't see a couple fields that they never use. Less clutter is always better!

If they are not required via a Validation Rule, then they are probably required via a Page Layout, or possibly if they are a picklist field, the Picklist Field requires a value in the in the "General Options" setting in the Field Setup and Config

You’d need a flow to utilise the custom field. But I am pretty sure NPSP caters for this out of the box.

If put in the org name in lead company field, the Npsp lead convert screen automatically gives you different options.

You’ll have the option to still create the household, AND the company account AND the affiliation record!

@Andrew Russo I thought that might be the case. I will look into using the contact then. Thanks! 

@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.

Yeah, you can't do this currently--ran into it myself. Your best bet to accomplish this declaratively is to run a daily scheduled flow that would check if a lead is more than 24 hours old and change the owner at that point. The challenge is you might have a lead that is up to almost 47 hours old if it were created a few minutes before the scheduled daily flow runs so it's not quite 24 hours old and then would wait until the next day's run to be 'caught'. Or, if you run it daily for anything created the day before you could have a lead come in after hours that nobody has had a chance to work with yet that would be reassigned too quickly. This may end up being a use case for which a scheduled Apex job is the best fit, or you'll have to accept some tradeoffs/limitations.

Yep, mapping is the way.  to the Account/contact or oppty.  Make sure the field types are the same.  Must map standard to standard or custom to custom.  Some stand fields auto-map and will not be in the field mapping section if you can't find them. 

Note that the Lead appears under "Recent Items". So this is not an actual search result being returned, but rather a reminder that you have recently worked with a Lead, which had that name.

Also keep in mind that having the "View and Edit Converted Leads" system permission could cause a converted Lead to keep showing up in your search results.