Skip to main content

Solution for ActionSupport on Lookups for a Visualforce Page

Hello there, There are two reasons why you are on this page, one is that you like to go through Force.com blogs and gain as much knowledge as you can. Its a good thing, only you won't gain any knowledge reading the blogs but by digging. Two, you are highly frustrated and have Googled extensively for keywords 'ActionSupport', 'Lookup' and 'Visualforce' for many hours and before that were struggling with ActionSupport, onblur, onChange and other events.

If you are here for second reason, we both sail in the same ship and even though I may sound like a telemarketer who is keen on wasting your time, I however, would like to inform you that I am sympathetic towards you. After having struggling to get this thing work on a Lookup for a long time, I decided to embark on the journey that took me back in time even before Salesforce.com existed. I went to the very depths of DOM and source code. Right to the birth place... ok not really, but I am just back from Star Wars Movie Marathon and still a bit woozie.

So anyways yes, the solution.

The code:
This is how your code will be looking right now:



<apex:pageBlockSection >



<apex:inputField value="{!someLookup__c}" >



<apex:actionSupport event="onChange" action="{!SomeAction}" rerender="thePageBlock" status="theStatus"/>         



</apex:inputField>



</apex:pageBlockSection>



<apex:pageBlock id="thePageBlock">



      //Something cool here.



</apex:pageBlock>  

So we need to do a bit of tweaking for this code and use the Big brother of ActionSupport, change the code to this

Corrected Code:

<apex:pageBlockSection >



        <apex:inputField value="{!someLookup__c}" onChange="someJs()"/>







<apex:actionFunction name="someJs" action="{!SomeAction}" rerender="thePageBlock" status="theStatus"/>    



         </apex:pageBlockSection>



<apex:pageBlock id="thePageBlock">



      Something cool here.



</apex:pageBlock>  

Obviously this is a workaround for the problem. There are some questions in the community as is this a bug in Salesforce? I don't think so.
Basically this has something to do with very primitive that is, native HTML. See lookup may be easy to build and render, but deep down it converts itself into a HTML component. In HTML it is split into two different components, one input field and another hidden field. As this is a complex rendering in itself, adding another event to it using actionSupport would be much tedious task.

If they do, obviously, its awesome.

Whats more?

Instead of actionFuction we can also call a native javascript code for the same. Well I changed my mood from aaarggh to Wuuu huuu.

Hope it makes you the happy as well. 

Toodles for now,
Siddhesh


Labels:

Comments

Post a Comment

Popular posts from this blog

The unofficial guide to become a Certified Salesforce Administrator (ADM 201)

In my attempt at maximum certifications in 60 days, I completed Salesforce Certified Administrator exam on February 11th 2013 So you have decided to ramp up your career and take certifications in your hand. Good choice. It is also likely that this is the first time you have heard of Salesforce, certification and since your company has a vision of you completing the certification you have decided to do it. At this stage it is likely that, You have done extensive googling. You have received countless brain-dumps. And you have received plenty of advise from different types of users which ranges from Admin certification is easier than making coffee to Admin certification is tougher than building a rocket-ship to fly off to the moon. The purpose of this guide is to give you a clear understanding of what to expect when you are expected to become Certified Salesforce Administrator. To bring sense to all the things you have seen so far and to clearly explain w...
72 comments
Read more

Some PDF tricks on Visualforce: Landscape, A4, page number and more

The beauty of Visualforce is simplicity. Remember the shock you received when you were told the entire page renders as PDF if you just add renderAs=PDF to the Page tag. For those who thought I spoke alien language right now, here is the trick, to render a page as PDF, we add a simple attribute to the <apex: page> tag <apex: page renderAs='pdf'> This will render the entire page as PDF. Now, say we need to add some extra features to the PDF. Like a page number in the footer or we need to render the page in landscape mode. Faced with this problem, I put on my Indiana Jones hat and went hunting for it in the vast hay-sack of the internet (read: googled extensively). Imagine my happiness when i found a big big page with many big big examples to solve the problem. The document I am referring to is from W3C, paged Box media . Long story short, I now possess the ultimate secret of rendering the page in any format I want. So here are few tricks I learned...
17 comments
Read more

What Toilet-Training my toddler Taught Me about change management

It was a Tuesday afternoon, and I had just finished a grueling design authority session when I smelled something foul. My poker-trained eyes spotted a tell on my toddler's face: He was about to soil his pants. I then ran behind my toddler, begging him to use the toilet. Trying various methods of persuasion, I begged him to use the toilet. This scene was familiar in our house ever since my partner and I began training him to use the toilet. He giggled, darting around like it was a game of tag. As I finally caught up to him and we triumphantly reached the bathroom, I realized this chaotic scene had uncanny parallels to change management in the workplace. It's not the act in itself but the various persuasion techniques and changing behavior embedded in my toddler's whole life. Here are some of the lessons my toddler taught me in change management. Change Takes Time Just as toddlers need time to adjust to potty use, employees and team members need time to adapt to changes. ...
Post a Comment
Read more