The optimizer tool WARNS that we have "Out-of-Date" API versions and recommends updating our Apex Classes, Triggers, and Visualforce pages.
Researching for "what issues Out-of-Date API versions might cause" I have found a wide range of opinions from “if it ain’t broke don’t fix it” to “better safe than very sorry trying to fix an urgent bug while at the same time wrestling with API version issues”.
Our consultant that developed the Apex code said they have never encountered an issue with "Out-of-Date" API versions.
I wonder what examples Salesforce experts can share on potential issues Out-of-Date API versions might cause, and how Admins can best justify updating the custom Apex code to management?
1 comment
I believe Kevin's advice was that it depends on how far out of date your API version is. If it's in the 15-18 range, then you might run into issues (security would be one possible area of concern) if you don't update. If it's just a few versions behind, then it becomes more of a "good to do" rather than a "must do" activity.
