◆ Salesforce

Populate record choice set from variable

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 taskPopulate the 'Product Options' record choice set in the 'New Order Flow' with active products…+
Populate the 'Product Options' record choice set in the 'New Order Flow' with active products from the 'Product2' object. The choices should display the product name and use the product ID as the value.
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 finalize this record choice set, help me make it resilient to data changes and user…+
Before I finalize this record choice set, help me make it resilient to data changes and user errors. What are the edge cases I should consider, like too many products or inactive products, and how can I ensure the choices always make sense to the sales rep using the flow?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe 'Product Category' choice set in the 'Product Inquiry' flow is showing duplicate values for…+
The 'Product Category' choice set in the 'Product Inquiry' flow is showing duplicate values for some categories.
The 'Product Category' choice set in the 'Product Inquiry' flow is showing duplicate values for some categories, which is confusing our support agents. I'm afraid of breaking the flow or introducing new data inconsistencies if I try to fix it without understanding the root cause. Is this likely a data issue, a filter problem, or a caching problem? What's the best next step to diagnose and resolve this without impacting agents during business hours?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternBuilding record choice sets for flows often leads to unexpected data issues or poor user…+
Building record choice sets for flows often leads to unexpected data issues or poor user experience.
Building record choice sets for flows often leads to unexpected data issues or poor user experience, requiring constant rework after deployment. We're always fixing what we thought was done. What habit should I change to ensure my record choice sets are robust, intuitive, and account for real-world data variations from the very beginning of the flow design process?
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.