◆ Salesforce

Query more than 50000 records

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 taskExport all 'Case' records created in the last year to a CSV file. Include 'Case Number',…+
Export all 'Case' records created in the last year to a CSV file. Include 'Case Number', 'Subject', 'Status', 'Account Name', and 'Created Date'.
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 get a full list of all 'Account' records that have had 'Closed Won' opportunities…+
I need to get a full list of all 'Account' records that have had 'Closed Won' opportunities totaling over $100,000 in the last three years, along with their 'Industry' and 'Annual Revenue'. This will help us identify our most valuable customer segments for the Q4 strategy meeting.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentOur marketing team needs a complete list of every 'Lead' and 'Contact' we've ever had for a…+
Our marketing team needs a complete list of every 'Lead' and 'Contact' we've ever had for a major data migration project.
Our marketing team needs a complete list of every 'Lead' and 'Contact' we've ever had for a major data migration project, and I know the total count is well over 100,000 records. My fear is that standard exports will time out or only give a partial list, leading to incomplete data for their project. I don't know the most reliable way to extract such a large volume of data without breaking it into multiple, error-prone chunks. What's the best next move to get all this data out reliably?
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 struggle with extracting large datasets for reporting or data projects, often…+
I frequently struggle with extracting large datasets for reporting or data projects.
I frequently struggle with extracting large datasets for reporting or data projects, often hitting limits or having to manually stitch together multiple smaller exports. This causes delays, frustration, and sometimes incomplete data for critical business decisions. What habit should I change in how I approach these large data extraction tasks, so I can consistently and efficiently pull comprehensive datasets without encountering system limitations?
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.