Starting November 20, the site will be set to read-only.
On December 4, 2023,
Apex Code Development (90768)
General Development (55146)
Visualforce Development (37251)
Lightning (18265)
APIs and Integration (17146)
Trailhead (11680)
Formulas & Validation Rules Discussion (11337)
Other Salesforce Applications (8116)
Jobs Board (6655)
Force.com Sites & Site.com (4842)
Mobile (2694)
You need to sign in to do that
Don't have an account?
johnc82 Will I run into any performance issue or any other problem by having the OnChange event on a lot of fields on a VF page? I'm calling a save function in my controller after a change on each field and doing a rerender of that page section. Is this ok?
why can't you give an option to user to perform all the changes and then go with one save....i think this will good...either user may come back and change the 2nd field after 4 th or 5th field changes are done..in this scenario unnecessary u are calling the controller.. hope you got my point
Yeah - that's perfectly fine. I can see a use case where you want to capture things in-flow.
If it were me and if I was employing a custom save method - I would have an Apex:outputPanel section at the top of my page to provide feedback to the user that fields were saving properly.
Something like creating an ActionFunction that calls the save - and rerenders the Apex:outputPanel section. Have each of the fields you're performing the onChange on now instead refer to the ActionFunction to get the rerender to fire.
In your save method - have it update a string (that's in the outputPanel) that gives some feedback.
-Andy