◆ Salesforce

Use 15-character ID in SOQL where clause

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 taskFind all 'Lead' records where the 'Owner ID' is '005f4000003hJgK' and the 'Status' is 'New'.…+
Find all 'Lead' records where the 'Owner ID' is '005f4000003hJgK' and the 'Status' is 'New'. Display their 'Name' and 'Email' fields.
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 acceptI need to retrieve a list of 'Contact' records associated with specific 'Account' IDs for a…+
I need to retrieve a list of 'Contact' records associated with specific 'Account' IDs for a report that goes to the regional VP. Before I run the query, ensure it's robust enough to handle both 15-character and 18-character IDs in the 'Account ID' filter, so I don't miss any relevant contacts if the input IDs vary.
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 pull all 'Opportunity' records related to a list of 'Account' IDs for the…+
My query for related records is returning incomplete data, and I suspect it's an ID length issue.
I'm trying to pull all 'Opportunity' records related to a list of 'Account' IDs for the quarterly review, but the results are missing several expected opportunities. The list of account IDs I'm using comes from an external system and might be 15 characters long. I'm afraid I'm silently dropping data, which would make our revenue projections look bad. What's the likely diagnosis, and what's the best next step to ensure my query correctly matches all IDs?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI consistently lose time debugging queries or integrations because of inconsistencies in ID…+
I frequently encounter issues with ID formats when integrating data from various sources.
I consistently lose time debugging queries or integrations because of inconsistencies in ID lengths – sometimes 15 characters, sometimes 18. This often leads to incomplete data sets or silent failures. What habit should I change to proactively handle these ID format variations, so I stop wasting hours on preventable data mismatches?
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.