SalesForce.Com Issues/Gotchas aka. Bugs/Defects (again !!!)
November 21, 2011
Yet another undocumented SalesForce Bug has been found !!!
This bring my personal count to 4 and climbing…
It is rather odd these kinds of defects can exist in such a prestigious framework as SalesForce/VisualForce/Apex with so many people using it when other web-based Frameworks (Django and others) do NOT exhibit such behaviors.
I have revised #2 and #3 while adding some additional issues since my last post: (This is where experience counts… since I know what is expected when unexpected things begin to happen…)
SalesForce.Com Issues/Gotchas aka. Bugs/Defects (Redux)
- Cannot reference null values for <apex:outputText/> or <apex:inputText/>.
- Cannot reference non-String objects with <apex:outputText/> or <apex:inputText/>.
- Under some circumstances VisualForce will allow String objects to be referenced by <apex:outputText/> or <apex:inputText/> tags however after a certain threshold has been reached the Force IDE will begin to complain about what it calls SObject references after which the only acceptable correction is to reference the result from a SOQL query – this can clash with #2 for some obvious reasons.
- VisualForce/Apex cannot handle instance variables that contain “_” underscores in variable names nor can Custom Field names be used from SOQL Queries in this manner.