◆ Salesforce

Select unique values in SOQL

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
See the prompt↓All Salesforce tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskSelect unique 'AccountName' values from the 'Opportunity' object where the 'Stage' is 'Closed…+
Select unique 'AccountName' values from the 'Opportunity' object where the 'Stage' is 'Closed Won'.
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 pull the list of unique account names for our marketing campaign, make sure the SOQL…+
Before I pull the list of unique account names for our marketing campaign, make sure the SOQL query only includes accounts from 'Closed Won' opportunities that have a 'Contract Start Date' within the last 90 days, so we target recent customers effectively.
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'm trying to get a list of unique account names from opportunities for a board report, but my…+
I'm trying to get a list of unique accounts for a report, but the query is returning duplicates and too many records.
I'm trying to get a list of unique account names from opportunities for a board report, but my SOQL query is returning duplicate account names and including accounts from opportunities that are still open. I'm afraid the report will be inaccurate and reflect poorly on our sales performance. What's the most robust way to ensure I only get truly unique account names for 'Closed Won' opportunities, and filter out any irrelevant stages or duplicates efficiently?
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 write SOQL queries for reports or integrations that either pull too much data,…+
My SOQL queries often return more data than needed or miss critical filters for reports.
I frequently write SOQL queries for reports or integrations that either pull too much data, miss crucial filters, or return duplicates, leading to inaccurate results and wasted time refining them. What habit should I change in my SOQL query construction process to consistently write precise and efficient queries that deliver exactly the unique data I need for a given business requirement?
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.