◆ Salesforce

Handle SOQL query zero results

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'm writing a SOQL query to pull open opportunities for the sales team dashboard. Show me how…+
I'm writing a SOQL query to pull open opportunities for the sales team dashboard. Show me how to handle the case where the query returns no results, so the dashboard doesn't break when there's nothing to display.
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 put this SOQL query into production for the new customer success portal, make sure it…+
Before I put this SOQL query into production for the new customer success portal, make sure it gracefully handles zero results. The portal needs to show a clear 'No open cases' message instead of an error, so our customers aren't confused or frustrated when they log in and see nothing.
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 new sales activity report is failing for some users, but not others, and I suspect it's…+
The new sales activity report is failing for some users, but not others.
The new sales activity report is failing for some users, but not others, and I suspect it's when their query returns nothing. I've added a null check, but it's still throwing an error. My team lead, Sarah, is pushing for this to be live by end of day. What's the best way to diagnose why the zero results handling isn't working as expected, and what's the most robust pattern for SOQL query zero result handling I should use?
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 get bug reports related to SOQL queries returning no data, leading to blank…+
I frequently get bug reports related to SOQL queries returning no data.
I frequently get bug reports related to SOQL queries returning no data, leading to blank screens or errors for users. It feels like I'm always patching these issues after deployment, which costs us time and user trust. What habit should I change in my development process to ensure I consistently build robust SOQL queries that gracefully handle zero results from the very beginning?
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.