You need to sign in to do that
Don't have an account?
Stevev
showHeader="false" inputField help text lost
In an Apex page does anyone know how to show the field help text (the standard question mark next to the field) when using <apex:inputField if the showHeader="false"? I noticed that in my apex code, fields show their help text when showHeaders="true" but disappears as soon as I set showHeaders to "false". Is there an attribute that needs to be set somewhere?
I am aware that Titles that do not show up when ShowHeaders is false, but help text not showing up is weird.
Anyways you could try using helpText attribute of page block section item to show the helptext. Below is an example
<apex:pageBlockSectionItem helpText="My Help Text">
<apex:outputLabel value="Account Number" id="AccNoLabel" for="AcctNo" />
<apex:inputField id="AcctNo" value="{!cs.Acct_Num__c}" required="true"/>
</apex:pageBlockSectionItem>
help text only displays if the showHeader attribute of the parent page is set to true
Thanks Rajesh,
There are a number of concerns with the approach you suggest:
I set up a test object to try out your suggestion (see below) but it wouldn't work for me and no help is displayed.
Thanks anyway.
You can find my replay content in Visualforce developer's guide,this mean helpText content will not display if showheared="false" .But you can try bind html tag title value like this:value="{!$ObjectType.Contact.Fields.New_Agency_Name__c.inlineHelpText}"
You suggest using the $ObjectType for inline help text. How would you apply your suggestion to the example code shown earlier?
There may to be a "solution" to this issue by building a Field map in Apex code but if I had to apply that to every field it would quickly become an unmanageable mess. What I would like to see is for SF to prescribe a Boolean value on each field to indicate he field help is displayed with a default of true but before I put that up as an Idea I want to explore what the available options are to resolve this problem.
I solved this by setting showHeader="true", but modifying the css
Awesome workaround!