◆ Salesforce

Dynamically get fields for SObject

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 need to get all the field names for the 'Opportunity' SObject. I'm building a dynamic query…+
I need to get all the field names for the 'Opportunity' SObject. I'm building a dynamic query for a report.
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 retrieve the fields for the 'Opportunity' SObject, make sure this approach is…+
Before I retrieve the fields for the 'Opportunity' SObject, make sure this approach is flexible. I need to get all field names, including custom fields, and it needs to be easily adaptable if I switch to a different SObject later, without hardcoding anything.
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 need to dynamically get all fields for an SObject type to build a flexible data export for…+
I need to dynamically get all fields for an SObject type to build a flexible data export, but I'm not sure how to reliably get both standard and custom fields without knowing them beforehand, and I'm worried about missing some.
I need to dynamically get all fields for an SObject type to build a flexible data export for the sales ops team, but I'm not sure how to reliably get both standard and custom fields without knowing them beforehand, and I'm worried about missing some critical ones. What's the most comprehensive and future-proof way to get all available fields for a given SObject, and what's the best way to ensure I capture everything they might need?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI repeatedly struggle with dynamically accessing SObject metadata, especially when needing to…+
I repeatedly struggle with dynamically accessing SObject metadata, especially when needing to work with fields without hardcoding their names, which makes my code less adaptable.
I repeatedly struggle with dynamically accessing SObject metadata, especially when needing to work with fields without hardcoding their names, which makes my code less adaptable and harder to maintain when new fields are added. What habit should I change to consistently and efficiently retrieve SObject field information dynamically, making my components more robust and less prone to breaking with schema changes?
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.