Salesforce Stack Exchange is a question and answer site for Salesforce administrators, implementation experts, developers and anybody in-between. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I scan my code, and I received a Serious issue:

<apex:inputText value="{!ld.Name}" />

I have applied FLS as the guide here :

<apex:inputText value="{!ld.Name}"  rendered="{!$ObjectType.Lead.fields.Name.Updateable}"/>

but it did not work.

share|improve this question

Using apex:inputText and apex:inputTextArea does not enforce FLS automatically.

Please note that using other input tags such as apex:inputText or apex:inputTextArea with SObject fields indicate to VisualForce that the fields should not be treated as SObject fields and prevent the platform to automatically enforcing FLS.

Is there a reason you would not want to use apex:inputfield? This would automatically enforce FLS

When rendering VisualForce pages, the platform will automatically enforce CRUD and FLS when the developer references SObjects and SObject fields directly in the VisualForce page.

share|improve this answer
how about property ? we can not put property into inputField. – manhnt Feb 13 '14 at 7:04

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

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