◆ Salesforce

Get dependent picklist options in Apex

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 me the dependent picklist options for 'Product Family' when 'Product Type' is 'Software' so…+
Get me the dependent picklist options for 'Product Family' when 'Product Type' is 'Software' so I can populate a custom field.
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 build this new component for the sales team, make sure the dependent picklist options…+
Before I build this new component for the sales team, make sure the dependent picklist options for 'Region' based on 'Country' are retrieved efficiently. I don't want any performance lag when reps are entering data.
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 creating a custom component for the order entry team that relies on a dependent picklist…+
I'm building a new custom component, and I need to display dependent picklist values, but I'm unsure how to retrieve them dynamically and handle all edge cases.
I'm creating a custom component for the order entry team that relies on a dependent picklist for 'Delivery Method' based on 'Shipping Carrier'. I'm worried about hardcoding values or missing some of the dependencies, leading to incorrect options for the reps. What's the most robust and future-proof way to dynamically fetch these dependent picklist options in Apex, ensuring all valid combinations are presented to the user without breaking if values change?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep getting burned by dependent picklists in custom development. Either I hardcode values…+
I frequently encounter issues with dependent picklists in custom development, either due to hardcoding or not handling all dependencies correctly.
I keep getting burned by dependent picklists in custom development. Either I hardcode values that later change, or I miss some of the intricate dependencies, leading to incorrect options for users and rework. What habit should I change to ensure I consistently retrieve and manage dependent picklist options dynamically and accurately in Apex, making my custom components more resilient to metadata 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.