Skip to main content

Override a standard button with Visualforce and Running round and round in circles

Are you that person who overrode the standard button with an awesome Visualforce page. Your page is beautifully working and then at the end want to send the user to the original page which you just override.


Hey you think to yourself, all I got to do to is, copy the original URL in address bar paste it in notepad and add it to the page. As simple as riding a bike.

If you did think this way, you are in for a surprise. Life is not exactly as easy as it seems, for when you override a standard Salesforce button or the link, you automatically override the original page too.

So your little plan goes down the drain and all we see in a infinite loop like this.


It was many many many years ago when I wasted an entire night in this vicious circle and decided to tell you a magic spell to help you out to break out of the circle.

When you pass on the URL of the original page in the Visualforce controller, simply add a URL parameter

noOverride=1

for e.g., suppose you want to pass it to a page, you might possibly want to pass it on to.
http://naX.salesforce.com/somePage

simply add
http://naX.salesforce.com/somePage&nooverride=1 to the page.

With this magic spell, your Visualforce page will magically transfer the control to the original page without redirecting it to itself.

Its been a while I am updating on this blog, but don't worry I have something special getting cooked for the developer community. I will be around. Thought many users are busy with #DF11 one small recipe will not harm anyone.

Toodles,
Sid
P.s. Talking about spells, Harry Potter 7 part II was released today. Sigh.

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…

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 from the page. To p…

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…