◆ Salesforce

Get yesterday's date in Apex

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 taskI need yesterday's date to filter the new leads for the daily sales report. Get me the Apex…+
I need yesterday's date to filter the new leads for the daily sales report. Get me the Apex code for that, so I can plug it into my query before I run it this afternoon.
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 I add this to the lead conversion process, help me get yesterday's date in Apex in a way…+
Before I add this to the lead conversion process, help me get yesterday's date in Apex in a way that handles different time zones consistently. I’ve had issues with dates shifting on reports for global teams, and I need this to be reliable for Mark in London and Sarah in New York.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe daily lead report for yesterday is showing zero results, but I know we had activity. I used…+
The lead report for yesterday is showing zero results, but I know we had activity.
The daily lead report for yesterday is showing zero results, but I know we had activity. I used the Apex code I found online for 'yesterday' and now I'm worried it's a time zone issue again, or maybe I'm misinterpreting how the date comparison works. My manager, David, is asking for this report by 3 PM. What's the most likely reason for the empty results, and what's the quickest way to confirm and fix the date logic?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep having to re-verify date logic in Apex when building new reports or features, especially…+
I keep having to re-verify date logic in Apex when building new reports or features.
I keep having to re-verify date logic in Apex when building new reports or features, especially around 'yesterday' or 'last week'. It feels like I'm always debugging off-by-one errors or time zone shifts, which eats up my sprint time. What habit should I change to ensure my date calculations are robust and reliable from the start, so I stop losing credibility with the business users over report accuracy?
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.