◆ Salesforce

Get sandbox name 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 taskGet the name of the current sandbox in Apex so I can display it in a debug log for the…+
Get the name of the current sandbox in Apex so I can display it in a debug log for the 'LeadProcessor' batch job.
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 the 'OrderFulfillment' Apex class runs, get the sandbox name. If it's a full copy…+
Before the 'OrderFulfillment' Apex class runs, get the sandbox name. If it's a full copy sandbox, I need to ensure a specific set of test data is loaded, otherwise, skip that step to avoid errors.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentOur new integration tests for the 'InvoiceGenerator' Apex class are passing in our dev sandbox…+
Our integration tests are failing in a sandbox, but passing in another, and I don't know why.
Our new integration tests for the 'InvoiceGenerator' Apex class are passing in our dev sandbox but failing consistently in our UAT sandbox. I'm afraid we're missing a critical configuration difference, and it's holding up deployment. How can I reliably get the exact sandbox name within the failing Apex context to pinpoint environment-specific issues without hardcoding?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI'm constantly having to manually check which sandbox I'm in to adjust deployment logic or load…+
I often find myself manually checking sandbox names to adjust deployment logic or test data.
I'm constantly having to manually check which sandbox I'm in to adjust deployment logic or load specific test data for Apex classes. This leads to errors when I forget or misidentify the environment. What habit should I change to make my Apex code more robust and environment-aware, so it automatically adapts without manual intervention?
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.