Skip to main content

List View Editing of Accounts

Imagine if you can have a list view of Accounts where users can view accounts, edit accounts in place? Well, it will be the most user friendly system.

Obviously, best practice is, open the list view with less fields and then allow users to edit the page with the less number of fields and if they wish to see details, have a detail page link.

The following code does just this for you.


VisualForce Page: inPlaceAccounts.page

<apex:page controller="AccountsController" tabstyle="Account">     
    <apex:sectionheader subtitle="{!$User.FirstName} {!$User.LastName}" title="Quick Edit Accounts">
    
<apex:pagemessages>
    <apex:form>         
    <apex:actionfunction action="{!saveEditAcc}" name="saveEdit">    
    <apex:pageblock title="Add New Account">  
        <apex:pageblocksection>
        <b>Name:</b> <apex:inputtext value="{!newAccount.Name}"> 
         <b>Annual Revenue:</b><apex:inputtext value="{!newAccount.AnnualRevenue}"> 
       </apex:inputtext></apex:inputtext></apex:pageblocksection>     
        <apex:commandbutton action="{!add}" value="Add">
    </apex:commandbutton></apex:pageblock>
    
    <apex:pageblock title="Existing Accounts">
    <apex:outputpanel id="projectList">
    </apex:outputpanel></apex:pageblock></apex:actionfunction></apex:form></apex:pagemessages>
<apex:repeat value="{!projects}" var="p">
        </apex:repeat><apex:outputpanel id="editRow" layout="none" rendered="{!p.Id == editAccount.Id}">               
  </apex:outputpanel>
<apex:outputpanel id="viewRow" layout="none" rendered="{!p.Id != editAccount.Id}">
            </apex:outputpanel>
<table><tbody>
<tr>         <th style="width: 40px;"></th> <th style="width: 40px;"></th>    <th>Name</th> <th>Annual Revenue</th> </tr>
<tr style="height: 20px;">              <td><apex:commandlink action="{!cancelEdit}" rerender="projectList">Cancel</apex:commandlink></td>      <td><apex:commandlink action="{!saveEditAcc}" rerender="projectList">Save</apex:commandlink></td>       <td><apex:inputtext onkeypress="if (event.keyCode == 13) saveEdit()" rendered="{!p.Id == editAccount.Id}" size="40" value="{!editAccount.Name}"></apex:inputtext></td>      <td><apex:inputtext onkeypress="if (event.keyCode == 13) saveEdit()" rendered="{!p.Id == editAccount.Id}" size="40" value="{!editAccount.AnnualRevenue}"></apex:inputtext></td>        <td><apex:commandlink action="{!del}" onclick="return confirm('Are you sure you want to delete this project?')">Del            <apex:param name="delid" value="{!p.Id}">          </apex:param>        </apex:commandlink></td>    <td><apex:commandlink action="{!editAcc}" rerender="projectList">Edit          <apex:param name="editid" value="{!p.Id}">       </apex:param></apex:commandlink></td>       <td>{!p.Name}</td>    <td>{!p.AnnualRevenue}</td>    <td><apex:outputlink target="_blank" value="/{!p.id}">View Details</apex:outputlink></td>     </tr>
</tbody> </table>
</apex:sectionheader>
</apex:page>

Controller:

Controller: AccountsController
public class AccountsController {
/*
@Author: Siddhesh Kabe
@Domain: http://force.siddheshkabe.co.in
Controller for Visualforce inPlaceAccounts.page 
*/
    public AccountsController() {
        newAccount= new Account(); //Create a new object for account.
    }

    public Account newAccount { get; set; }    //A Account variable to add a new account in the place.
    public Account editAccount { get; set; }    //A temporary variable to store the existing account in place.
    
    
    /*
    @Function: getProjects
    @params: None
    @Return Type: List of Accounts to display
    @Usage: The getter method to fetch Accounts. 
    */
    public Account[] getProjects() {
        return [SELECT Name,AnnualRevenue from ACCOUNT WHERE OwnerId = :UserInfo.getUserId() ORDER BY CreatedDate DESC]; 
    }
    
    
    /*
    @Function: getParam
    @Param: String, the Parameter name to fetch value from.
    @Return Type: String, The value of the URL paramter.
    @Usage: The getter method to fetch Accounts. 
    */
    public String getParam(String name) {
        return ApexPages.currentPage().getParameters().get(name);   
    }
    
    /*
     Action method to add new account. 
    */
    public PageReference add() {
        try {
            INSERT newAccount;
            // if successful, reset the new Account for the next entry
            newAccount = new Account();
        } catch (Exception e) {
            ApexPages.addMessages(e);
        }
        return null;
    }
     
    /*
     Action method to del a account. 
    */
     
    public PageReference del() {
        try {
            String delid = getParam('delid');
            Account delAccount = [SELECT Id FROM Account WHERE ID=:delid];
            DELETE delAccount;
        } catch (Exception e) {
            ApexPages.addMessages(e);
        }
        return null;
    }
    
    /*
     Action method to edit a account. 
    */      
    public PageReference editAcc() {
        String editid = getParam('editid');
        editAccount= [SELECT Name,AnnualRevenue FROM Account WHERE Id=:editid];
        return null;
    }
    
    /*
     Action method to cancel new account. 
    */
     public PageReference cancelEdit() {
        editAccount= null;
        return null;
    }
    
    /*
     Action method to save the edited account. 
    */
    public PageReference saveEditAcc() {
        try {
            UPDATE editAccount;
            editAccount= null;
        } catch (Exception e) {
            ApexPages.addMessages(e);
        }
        return null;
    }
}






This code will nearly do the trick.

Hope it helps,
Cheers,
Sid

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…