[SalesForce] Unknown Property on Controller Extension

So I have a standard controller and an extension that I'm trying to use to call back a list from a different object to use in a PageBlockTable. In the visualforce page I declare my standard controller and extension:

<apex:page standardController="APM__c" extensions="APM_OpenChart" recordSetVar="apps">

Later on in my PageBlockTable I'm trying to pass the list from the extension using this class:

public with sharing class APM_OpenChart {

    public APM_OpenChart(ApexPages.StandardSetController stdController) {}

    public List<APM__c> spoofgrid(){
         List<APM__c> results = database.query('SELECT Name , BV_Result__c ,TV_Result__c FROM APM__c Limit 1');
        return results;
    }
}

However, when I attempt to pass the values I get an unknown property error when trying to use the list from the extension.

<apex:pageBlockTable value="{!APM_OpenChart.spoofgrid}" var="token">

Best Answer

Change you method to getspoofgrid. Add get so it will be accessible in page

public List<APM__c> getspoofgrid(){
         List<APM__c> results = database.query('SELECT Name , BV_Result__c ,TV_Result__c FROM APM__c Limit 1');
        return results;
    }

And in VF

<apex:pageBlockTable value="{!spoofgrid}" var="token">

Related Solutions

[SalesForce] The standard list controller and Custom Buttons on Related Lists

I completely agree. If you're not acting on a specific set of record in the related list with your custom button, i.e. if you're building a custom New button, there really isn't any need for a standard set controller. IMHO, salesforce should just have a standard way of passing over the details to a custom button and leave the visualforce page developer to figure out whether to implement with a custom controller, standard controller, or standard set controller depending on their specific requirements.

So why is it needed? I can only guess, but I would assume it's to prevent administrators from accidentally wiring up a button to a visualforce page that may not be able to accept your input.

That said, there are two ways to work around this. First, use a url for the source of your button. Using your example of a new task button on say an account record you could do

/apex/myCustomNewTaskPage?id={!Account.id}

Second, you can create the page and set the recordset var, create the button, then just edit your page. Once the button has been set up it doesn't enforce maintaining the recordsetvar attribute (although it may complain if you try and edit the button later).

[SalesForce] custom controller with extension

It is possible to have an extension for a custom controller.

Let's say my custom controller is this:

public with sharing class MyController {
...
}

My extension could then have a contructor that is called when this class is the controller for a page:

public with sharing class MyExtension {
...
  public MyExtension(MyController ctrlParam) {

  }
}

You could have the same extension work for both ApexPage.StandardController and some custom controller, but you'd need to overload the constructor:

public with sharing class MyExtension {
...
  public MyExtension(MyController ctrlParam) {

  }

  public MyExtension(StandardController ctrlParam) {

  }
}

If you want your extension to be reused for a lot of controllers, you might need to plan ahead and use inheritance either from a superclass or an interface so that you don't end up with too many constructors.

I suspect that most customer implementations do not get to this degree of sophistication. Where I would expect this model to crop up more often is in AppExchange app architecture.

Best Answer

Related Solutions

[SalesForce] The standard list controller and Custom Buttons on Related Lists

[SalesForce] custom controller with extension

Related Topic