◆ Salesforce

Upgrade API version on Apex classes

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskUpgrade all Apex classes related to the 'Opportunity Management' feature to API version 58.0 to…+
Upgrade all Apex classes related to the 'Opportunity Management' feature to API version 58.0 to align with the latest platform release.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore we upgrade all our Apex classes to API version 59.0 for the Spring '24 release, identify…+
Before we upgrade all our Apex classes to API version 59.0 for the Spring '24 release, identify any classes that might rely on deprecated methods or old platform behaviors. Flag those for review and suggest alternatives, so we don't introduce unexpected bugs after the upgrade.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI upgraded the 'AccountProcessor' Apex class to API version 59.0, and now the nightly batch job…+
I just upgraded a critical Apex class to API version 59.0, and now a related batch job is failing intermittently with a 'System.LimitException' error that wasn't there before.
I upgraded the 'AccountProcessor' Apex class to API version 59.0, and now the nightly batch job that uses it is intermittently throwing 'System.LimitException' errors, which never happened before. I'm afraid this upgrade introduced an unexpected governor limit issue, and I don't know which specific change in the new API version caused it. What's the likely diagnosis, and what’s the best next move to identify and fix the underlying cause?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternWe consistently face unexpected issues, like governor limit breaches or subtle behavior…+
Every time we upgrade the API version of our Apex classes, we encounter unexpected regressions or governor limit issues that delay our releases.
We consistently face unexpected issues, like governor limit breaches or subtle behavior changes, whenever we upgrade the API version of our Apex classes. This always delays our release cycles and creates post-deployment stress. What habit should we change to proactively identify and mitigate these risks before we commit to a full API version upgrade across our codebase?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from Salesforce's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.