◆ Salesforce

Evaluate sObject Collection Variable for null

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 taskCheck if the 'Account Contacts' collection variable is null before trying to loop through it in…+
Check if the 'Account Contacts' collection variable is null before trying to loop through it in the 'Update Related Cases' flow.
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 acceptWhen the 'New Opportunity' flow runs, if the 'Related Products' collection is empty, I don't…+
When the 'New Opportunity' flow runs, if the 'Related Products' collection is empty, I don't want to create an empty product line item. Can you add a check for that before the create record element to avoid unnecessary data?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentSales reps are getting 'null pointer' errors in the 'Convert Lead' flow, specifically when it…+
Users are reporting errors in a flow when they create a new lead, and I suspect an empty record collection is the culprit.
Sales reps are getting 'null pointer' errors in the 'Convert Lead' flow, specifically when it tries to create related tasks. I suspect the 'Lead Tasks' collection variable is sometimes null, but I can't reliably reproduce it. I'm afraid this is causing lost follow-ups. What's the most robust way to check for a null collection variable in a flow to prevent this specific error?
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 getting caught by flows failing because I forget to check if a collection…+
I frequently forget to check if a collection variable is null before using it, leading to runtime errors.
I'm constantly getting caught by flows failing because I forget to check if a collection variable is null before iterating or trying to access its elements. It's a consistent source of bugs and lost time debugging. What's a better habit or pattern for handling collection variables in flows to prevent these 'null' errors from derailing my work?
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.