◆ Salesforce

Mass update records via list view

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 taskMass update opportunity records via a list view. Open the Enterprise Opportunities list view,…+
Mass update opportunity records via a list view. Open the Enterprise Opportunities list view, filter to Close Date this quarter and Stage equals Negotiation, select all 120 visible records, change the Stage to Proposal and add a note in the Comments field: 'Stage progressed per pipeline review, contact client for revised close date.' Perform the update and confirm that 120 records changed, then notify the sales ops channel.
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 mass-update stages on the Negotiation list, reduce the chance of mistakes: show…+
Before I mass-update stages on the Negotiation list, reduce the chance of mistakes: show Opportunity ID and Owner in the view, add a validation column that flags closed-stage mismatches, run a sample update on 10 records and report which owners were affected, and produce a CSV backup of the 120 records to the shared drive in case we need to revert.
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 attempted a mass update of 120 negotiation-stage opportunities but it failed halfway and left…+
Mass update failed midway with partial saves
I attempted a mass update of 120 negotiation-stage opportunities but it failed halfway and left about 40 records unchanged. I don't know whether this is a permissions issue, a validation rule, or a platform timeout. The reps expect a clean pipeline for tomorrow's forecast. What is the most likely cause and the immediate steps to finish the update safely?
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 have to revert mass updates because validation rules or missing fields block some…+
I keep reverting mass updates because of missed validations
I frequently have to revert mass updates because validation rules or missing fields block some records, and that creates distrust from reps. I waste hours backing up and redoing changes. What process or checklist should I adopt so mass updates succeed first time and I stop breaking the pipeline?
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.