Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to make 'Last Name' field in 'Create Lead' form non-mandatory #999

Open
SonalikaG opened this issue Jun 22, 2022 · 10 comments
Open

How to make 'Last Name' field in 'Create Lead' form non-mandatory #999

SonalikaG opened this issue Jun 22, 2022 · 10 comments

Comments

@SonalikaG
Copy link

Hi, is there a way to make the 'Last Name' field in Create Lead form non-mandatory? Currently, we cannot submit a Lead without providing data in the 'Last Name' field. Please suggest a way.

image

@SonalikaG SonalikaG changed the title Make 'Last Name' field in 'Create Lead' form non-mandatory How to make 'Last Name' field in 'Create Lead' form non-mandatory Jun 22, 2022
@srbaker
Copy link

srbaker commented Apr 14, 2023

I'm a fan of this, but I think an even better solution is to just merge First Name Last Name into "Name." Would such a patch be reasonable?

@johnbumgardner
Copy link
Member

Yeah I like this idea. Probably scales better to non western cultures too

@johnbumgardner
Copy link
Member

johnbumgardner commented May 28, 2023

tagging this with good first issue. @srbaker if youre interested in implementation please be our guest

@srbaker
Copy link

srbaker commented Jun 5, 2023

I'm going to take a crack at this. Thanks!

@johnbumgardner
Copy link
Member

I'm going to take a crack at this. Thanks!

awesome, feel free to reach out to me if you have questions

@clevertension
Copy link

@johnbumgardner so i think it is good idea to merge First Name and Last Name to Name, so i can implement it

@ferrisoxide
Copy link
Contributor

ferrisoxide commented Aug 11, 2023

Is merging first and last names potentially a bit "lossy"? I understand that there's some value in just having a name, but are there cases where being able to identify a lead's first name might be useful?

I'm thinking of the use case where you are constructing an email campaign. Reaching out to someone with the greeting "Hi Elizabeth Blackwell" is more formal than "Hi Elizabeth". If you are going for a more personal approach, using someone's full name might not be ideal.

I wonder if just making last_name optional might be a more flexible alternative than combining first and last names. Or perhaps the naming scheme could be configurable. I don't necessarily have a solution here - just thinking things through in my own head.

@ferrisoxide
Copy link
Contributor

ferrisoxide commented Aug 13, 2023

Something else to consider: if we flatten first_name and last_name to just name we will have to do the same for Contact, otherwise we won't be able to convert Leads to Contacts.

@CloCkWeRX
Copy link
Member

I'm open to a pull request adding a "display_name" or similar, which can be new/distinct from the structured named elements.
Over time, this can evolve to be the default.

Be aware of
https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/

@ferrisoxide
Copy link
Contributor

The original request from @SonalikaG was fairly simple. Is there a danger we'll end up complicating things in the search for a more comprehensive solution that we don't have a current requirement for?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants