◆ Salesforce

Select into Map using Database.query()

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 taskWrite a Database.query() statement to select the names and emails of all active customers into…+
Write a Database.query() statement to select the names and emails of all active customers into a Map, using their customer ID as the key.
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 this goes into production, make sure the Database.query() selecting into a Map is…+
Before this goes into production, make sure the Database.query() selecting into a Map is resilient to cases where a customer ID might be duplicated or missing, so we don't get runtime errors during the nightly sync.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentMy Database.query() selecting into a Map is throwing a 'duplicate key' error during testing,…+
My Database.query() selecting into a Map is throwing a 'duplicate key' error, and I'm not sure how to handle it.
My Database.query() selecting into a Map is throwing a 'duplicate key' error during testing, and I'm not sure how to handle it. I need this to pull customer data for the marketing team's new campaign by tomorrow, and a delay means missing their launch window. I'm afraid of breaking the existing data processing. What's the likely diagnosis for a duplicate key error when selecting into a Map with Database.query() and what's the best next move to resolve it without causing new issues?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI frequently run into issues when using Database.query() to select into Maps, especially when…+
I frequently run into issues when using Database.query() to select into Maps, especially with data variability.
I frequently run into issues when using Database.query() to select into Maps, especially when dealing with inconsistent data that can lead to unexpected keys or values. This often slows down development. What habit should I change to improve my efficiency and reduce errors when selecting into Maps using Database.query()?
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.