Passing method parameters with apex:actionFunction

  • I have this Visualforce code snippet in a page:

    <apex:outputLink value="javascript:if (window.confirm('Are you sure?')) DeleteQuoteLineItem('{!LineItem.QuoteLineItem.Id}');">
    <apex:actionFunction action="{!DeleteQuoteLineItem}" name="DeleteQuoteLineItem" reRender="content">
        <apex:param value="test"/>

    The two methods I'm using for testing are:

    public void DeleteQuoteLineItem(String RecordID)
        System.debug('method with a paramater');
    public void DeleteQuoteLineItem()
        System.debug('method without a parameter');

    Everytime I click on the link to execute the apex:actionFunction, it's calling the DeleteQuoteLineItem() method without any parameter. I looked online and it seems like I need to create a class attribute and use assignTo= in my apex:param to populate it accordingly.

    Is it possible to prevent this behavior and use standard method parameters, so I don't have to create class attributes? I want to work on a clean and optimized codebase, preventing unnecessary variable scope (so no class attribute when it's not required) and improve code re-usability by staying context agnostic.


    Just curious, but what's the use case. Why are you opposed to using a class property to assign the param to? Or are you just curious if it's possible?

    It's just to make sure that data that do not require such a scope doesn't end up in a class attribute. I don't need the value sent by my `action:actionFunction` to be available in all the class, it's pointless :)!

    ok, I was just curious. Added an answer that hopefully helps.

  • You can access the param that was passed directly inside you controller using the ApexPages class or the system class.


    <apex:outputLink value="javascript:if (window.confirm('Are you sure?')) DeleteQuoteLineItem('TEST VALUE');">
        <apex:actionFunction action="{!DeleteQuoteLineItem}" name="DeleteQuoteLineItem" reRender="content">
            <apex:param name="myParam" value=""/>


    public void DeleteQuoteLineItem(){
        //either of the next 2 lines will work, 
        string passedParam1 = Apexpages.currentPage().getParameters().get('myParam');
        string passedParam2 = system.CurrentPageReference().getParameters().get('myParam');

    Im just curious as to why you are opposed to using class properties to assign the params to. Both ways will work, just curious if you have a unique use case or just curious of other ways of accomplishing it. Hope this helps

    Because the argument doesn't require such a scope within the class. Just like any other language, you shouldn't unnecessarily increase the scope of a variable when it doesn't need such a scope. Any other method inside this class could mess with the value. That's what method arguments are for, to prevent that.

    You don't need to assign it to a variable, you can pass it directly to a method or however you want to use it. If you don't want to assign it to a variable, then don't assign it to a variable. This allows you to pass the value to a controller without using a class attribute, which is what I thought you asked in the question.

    Using `ApexPages` brings another issue: non-agnostic context. If I want to call this method from a trigger, I'll hit an error. Just trying to follow good practices and improve code reusability.

    I get that, but I would update your question to include these parameters for people to consider. Your question is much more general, and now you're bringing in new requirements in comments. I would update the question to explain exactly what you are looking for to avoid lengthy comments like this.

License under CC-BY-SA with attribution

Content dated before 7/24/2021 11:53 AM