Why in case of web-to-lead we can enter null value in the web-lead page, but the Salesforce field it looks like the image below? Null Lead


The answer is NO

The Lead object has two required fields

  • Company
  • LastName

without these values, the Lead record cannot be saved

The W2L servlet coerces value of [not provided] into the Lead.Company and Lead.LastName fields so as to ensure a lead created on a W2L form is saved (e.g., perhaps only an email + description is provided by the user)

If you want to make sure that W2L leads include a "real" value for Company and LastName, you need to extend the HTML that the W2L process generates. See SFDC help doc on how to do this (or see this SFDC Success post

  • But why it is accepting null value from web-to-lead and populating the field with [not provided]? Jan 7 '20 at 17:04
  • 1
    Because the SFDC-supplied W2L servlet coerces that value to ensure a Lead is saved. The W2L form needs to be extended to enforce a value in the user's browser.
    – cropredy
    Jan 7 '20 at 17:12
  • So it is salesforce's default strategy for not losing a lead then. Thank you very much Sir. Can you please look at my other question regarding to queues. Jan 7 '20 at 17:19
  • Sam - as a service to the Community, you should accept the answer so others can benefit from your question; I see other contributors are looking at your Queue question
    – cropredy
    Jan 7 '20 at 18:14

Its not null values. Its just placeholder text that will be stored is required fields since it cannot be blank.

  • What is a place holder value and when/in which case salesforce use it? Jan 7 '20 at 17:03

Not the answer you're looking for? Browse other questions tagged or ask your own question.