◆ Salesforce

Get record ID in LWC

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 record ID of the current page in the 'CaseDetails' LWC so I can display case-specific…+
Get the record ID of the current page in the 'CaseDetails' LWC so I can display case-specific information.
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 acceptWhen the 'CaseDetails' LWC is placed on a standard case record page, automatically retrieve the…+
When the 'CaseDetails' LWC is placed on a standard case record page, automatically retrieve the ID of that specific case. This needs to happen without explicit user action, so the LWC can immediately display details relevant to the case the support agent is viewing.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentA support agent just reported that our new 'CaseDetails' LWC is showing generic data, not the…+
A support agent reported our new LWC is showing generic data, not for the current case.
A support agent just reported that our new 'CaseDetails' LWC is showing generic data, not the details for the specific case they're currently viewing. I'm afraid this will make them lose trust in the tool and impact their efficiency. I can't tell if the LWC isn't correctly getting the record ID, if the data query is wrong, or if it's a caching issue. What's the likely diagnosis for the LWC displaying incorrect data, and what's the best next move to ensure it shows the current case's details by end of day?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternOur LWCs often struggle to correctly identify the context of the record they're placed on,…+
LWCs frequently struggle to correctly identify the context of the record they're on.
Our LWCs often struggle to correctly identify the context of the record they're placed on, leading to incorrect data display and user confusion. I keep losing time debugging why LWCs aren't showing the right information for the current record. What habit should I change to consistently and reliably get the current record ID in LWCs, ensuring they always display relevant data?
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.