Skip to main content

Easiest AJAX Pagination on Visualforce

There are two ways of writing a code, the hard way and the best way, Of-course the hard way is the easy way and best way if always hard way. If this sentence seems hard to understand, understand it is for the best.

When developing a VF page, the most important we need is pagination, throwing the large chunk of data on user screen is going to give the user goose bump. After trying a dozen method I came to know the easiest way of implementing pagination using standard set controller on a custom controller.

The demo of the code is available here

The visualforce Page:

<apex:page controller="OpportunityPagination" showheader="false">
            <apex:pageblock id="ThePageBlock">
                <apex:pageblocktable value="{!opportunities}" var="o">
                    <apex:column value="{!}">
                    <apex:column value="{!o.closedate}">
                <apex:panelgrid columns="5">
                        <apex:commandlink action="{!first}" rerender="ThePageBlock"> First</apex:commandlink>
                           <apex:commandlink action="{!previous}" rendered="{!hasPrevious}" rerender="ThePageBlock">  Previous</apex:commandlink>  
                            <apex:outputtext value="Page #{!pageNumber} ">                 
                            <apex:commandlink action="{!next}" rendered="{!hasNext}" rerender="ThePageBlock">Next </apex:commandlink>
                             <apex:commandlink action="{!last}" rerender="ThePageBlock">Last </apex:commandlink>

Apex Controller:

public class OpportunityPagination{ 

    public ApexPages.StandardSetController Con{
        get {
            if(con== null) {
                con= new ApexPages.StandardSetController(Database.getQueryLocator([select name,closedate from Opportunity]));
            return con;
    public List getOpportunities() {
         return (List) con.getRecords();
     /*** Pagination control***/
     // indicates whether there are more records after the current page set.
    public Boolean hasNext {
        get {
            return con.getHasNext();
    // indicates whether there are more records before the current page set.
    public Boolean hasPrevious {
        get {
            return con.getHasPrevious();
    // returns the page number of the current page set
    public Integer pageNumber {
        get {
            return con.getPageNumber();
    // returns the first page of records
    public void first() {
    // returns the last page of records
    public void last() {
    // returns the previous page of records
    public void previous() {
    // returns the next page of records
    public void next() {;
    // returns the PageReference of the original page, if known, or the home page.
    public void cancel() {
 /*** Pagination control***/


  1. What about return a list of all pages so that the users could click on page 3, 4 etc

    1. You could write a maths function for that. You have total number of pages and use function getResultSize() and getPageSize() to determine how many pages are in the list. And I think setpageNumber() should navigate to the desired page number


Post a Comment

Popular posts from this blog

Video: Top ten tips on how not to ruin Salesforce implementation

Another presentation for the London Salesforce Developer Group using mobile app. 
When it comes to Salesforce development, we all know what it takes to deliver stuff. Having a certified professional helps you gain a knowledgeable partner but what about the things such as common sense?  We all know how to deliver things on client requirements but what about things that are not mentioned by the client. We will be discussing in details things that will enhance the user experience, focus on tips to read your customers mind and have a bit of perspective on the user experience.

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…

Four secrets to improve the usability of your visualforce/Lightning pages on Salesforce

In the immortal words of a certain machine returning back in time, I am back. For now. After procrastinating for over a year and drafting a lot of rants- I am back with a very important coding lesson for you. For now.

When we are designing a Visualforce page or an app or a lightning component (added that only to trick google) or any web page for that matter, we often tend to wrap up things quickly. Ask anyone on the team, how to design a good User Experience? and the person will immediately throw buzz words like Bootstrap, angular and other useless libraries (did someone squint?)

Ok, Bootstrap, Angular-Js, and all the libraries are really cool and are useful in designing a fabulous UI. They are helpful in creating responsive pages that will work on all the devices but this post is not about those. Nope. For the purpose of this post, all the external libraries and buzzwords you use to decorate your resume are useless. (Adding Angular JS in your resume for a Salesforce consultant posit…