◆ Salesforce

Query picklist value not API name

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 taskGet the display label for the 'New' status on the 'Case' object's 'Status'…+
Get the display label for the 'New' status on the 'Case' object's 'Status' picklist.
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 the user-friendly label for the 'Closed Won' stage on the 'Opportunity' object.…+
I need to get the user-friendly label for the 'Closed Won' stage on the 'Opportunity' object. Make sure it's the text a user sees, not the internal API name, because I'm displaying it in a report for Sarah in sales.
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'm building a custom component to show the 'Industry' for an Account, but it's displaying…+
I'm trying to display a picklist value, but it's showing the API name instead of the label.
I'm building a custom component to show the 'Industry' for an Account, but it's displaying 'Technology_Services' instead of 'Technology Services'. I used `Account.Industry__c`, but that's giving me the API name. How do I get the actual human-readable label that's set up in the picklist configuration, and what's the best way to ensure I always get the right version for display?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternMy users often complain that picklist values in my custom components are hard to understand…+
I frequently display picklist API names instead of their labels, confusing users.
My users often complain that picklist values in my custom components are hard to understand because they see API names instead of labels. This leads to support tickets and rework. What habit should I adopt to consistently retrieve and display the correct picklist labels, ensuring clarity for the sales team and avoiding unnecessary confusion?
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.