◆ Salesforce

Pass variable from LWC to Screen Flow

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 taskPass the 'selectedProductId' variable from the 'Product Selector' LWC to the 'Order…+
Pass the 'selectedProductId' variable from the 'Product Selector' LWC to the 'Order Confirmation' screen flow for the new checkout process.
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 deploy this, make sure the 'selectedProductId' variable passed from the LWC to the…+
Before I deploy this, make sure the 'selectedProductId' variable passed from the LWC to the screen flow is robust. Can you also ensure it handles cases where no product is selected, preventing errors in the 'Order Confirmation' 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 'Order Confirmation' screen flow is failing randomly, and I'm afraid it's because the…+
The 'Order Confirmation' screen flow is failing intermittently, and I suspect the variable from the LWC isn't always passing correctly.
The 'Order Confirmation' screen flow is failing randomly, and I'm afraid it's because the 'selectedProductId' variable from the 'Product Selector' LWC isn't always getting through. I can't tell if it's a null value or a mismatch. What's the best way to debug this in real-time and confirm the variable is consistently received and correctly formatted by the flow?
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 losing time debugging data transfer issues between LWCs and screen flows, especially…+
I frequently encounter issues with data not correctly transferring between components and flows.
I keep losing time debugging data transfer issues between LWCs and screen flows, especially when variables aren't passing as expected. This consistently delays new feature deployments and frustrates the sales team. What habit should I change to proactively build in better validation and error handling for variable passing, ensuring smoother integration from the start?
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.