◆ Salesforce

Implement general trigger bulkification

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 taskMake sure the new 'Update Account Status' trigger can handle 200 account updates at once…+
Make sure the new 'Update Account Status' trigger can handle 200 account updates at once without failing. Test it with a large data set.
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 'Update Account Status' trigger goes live, review its current logic. What are the…+
Before this 'Update Account Status' trigger goes live, review its current logic. What are the potential governor limit issues if 500 accounts are updated simultaneously, and how can we optimize it to prevent those failures and ensure data integrity?
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 'Update Account Status' trigger I just wrote is failing with governor limit errors when the…+
The new trigger I wrote for updating account status is failing when the marketing team runs a bulk update.
The 'Update Account Status' trigger I just wrote is failing with governor limit errors when the marketing team tries to update more than 100 accounts at once. They need to run these bulk updates regularly, and I'm afraid of data loss or system outages. I thought I handled it, but clearly missed something. What's the core issue, and what's the most robust way to ensure this trigger can handle large volumes without breaking?
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 run into governor limit issues with triggers during bulk data operations,…+
Triggers I write frequently hit governor limits during bulk operations.
I consistently run into governor limit issues with triggers during bulk data operations, leading to frustrated users and emergency fixes. It feels like I'm always patching. What habit should I change in my trigger development process to proactively implement bulkification and error handling from the start, so I'm not constantly reacting to failures?
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.