Filter in ListView Account Name

Hi Rodrigo, 

By default the Account Name in Leads module is a Text field, not a relationship to the Accounts module. 
From what you are sharing, it seems they would like to have it being a relationship instead? To be similar to Contacts module for example? 

Am I understanding the scenario correctly?

Cheers, 

André 

Andre Serrazina  that is correct. 

Hey Rodrigo,

 This is a wild guess as I have no visibility on the number of Lead records and the relationships in place in the instance, however, a possible way forward could be:

1 – For new Lead records, creating a new Leads > Accounts Relationships and add it to the Record view to replace the “Account Name” field.

Users should start using the relationship for creating and Searching for Leads.

2 – This will leave you with a problem to solve for the existing records. For that I have thought about two parallel approaches:

• If you already have a Lead > Contact > Account pathway, you could leverage this by pulling relationship via script from the Contact and applying it to the Leads.
• If we’re only dealing with the “Account Name” at the Lead level, one workaround could be to run a PostMan script that would query the Accounts Module and link up the new Relationship with the retrieved Accounts.
   

A quick heads-up with this method: it requires careful supervision because any mismatch like typos might mean the right Account will not be found/linked.

It's definitely worth experimenting with in a test environment to see if it aligns with what you customer needs.

Let me know what you think.

Cheers,

I see a few problems with the approach of having a relationship between Leads and Accounts, not the least of which would be the effect it would have on the Lead Conversion process.

The intent of having the Account field as freeform is that you can populate that field from web forms and other lead sources without worrying too much about adding "junk" to your Accounts module.

I see Leads as a bit of a dumping ground, while Contacts/Accounts are a much more solid, curated, list of people/entities we have done business with or are actively trying to do business with (we determined that an Opportunity exist).

By not relating the Lead to an Account you can have more control over what Accounts are created, and more control over the standardization of names.

If the problem is that you have a team who qualifies Leads and tries to map Account Names for a cleaner Lead Conversion, I can see why you would want the auto-populate that the Relate Field affords.

If I had to work on something like this I would try to see if I could devise a query-based validation of the Account Name.

Perhaps add a new non-db query based Dropdown Field that could look up the existing Account Names and suggest possible matches, then copy the selection from that Dropdown to the text-based Account Name while still allowing the user to override the value in the text field and therefore add a new Account Name if needed... could be a bit of a convoluted solution but perhaps less so than making Account a relate field?

This is just a quick brainstorm on my part, so don't take it too seriously, it would need to be thought through a bit more...

FrancescaS

Thank you, I will think about it. 

Thank you,

On point as always, thanks for sharing Francesca Shiekh .