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 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 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:pageBlock id="thePageBlock">
      //Something cool here.

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:pageBlock id="thePageBlock">
      Something cool here.

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,


Post a Comment

Popular posts from this blog

The curious case of the custom redirection on Salesforce Console

Every developer worth their salt knows that the easiest way of redirection from a page to another is by using everyone's favorite function

public PageReference redirect() { PageReference pageRef = page.peskyProblemRedirection; pageRef.setRedirect(true); return pageRef; }
And the method is called by adding it to the Action attribute of the CommandButton or link, which works like charm and the user is redirected to the page after completion of the action.
So why am I going back to the basics? Because this way of redirection causes a pesky little problem in using the Service Cloud or Sales Cloud console.

Let's illustrate the problem, let's say you have a visualforce page as follows:

<apex:page sidebar="false" showHeader="false" controller="myExampleController"> <apex:form > <apex:pageBlock > <apex:pageBlockButtons > <apex:commandButton action="{!Redirect}&qu…

Cache me if you can: What you should know before daring to set URL parameter on visualforce

If someone gave me a pence for every time there was an SOQL query in an APEX Class without using Limit or a condition during a code review, I could afford a Lamborgini this month. Sigh. If only. We make it a habit of going digging for data, at the very moment we need it. The crux of this problem happens when you have chain classes which are independent of each other. Each class needs the reference from a single record and we have to query for that record every single time.

While we don't see it, every SOQL query has a cost to it, and it does not go in my Lamborghini fund, however, it should. In a recent project, we had to construct an Account 360 page that could fetch information from different integration points. The page was also called using a live telephony integration, which could pass the phone number for the account. This required an ability to keep in context the Account that was on call.

Passing the Account id in URL parameter was a valid option, however, any manipulatio…

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 what to do and what not to do.