◆ Salesforce

Retrieve Geolocation fields from 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
See the prompt↓All Salesforce tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskCreate a new Lightning Web Component to display the account's primary office location…+
Create a new Lightning Web Component to display the account's primary office location coordinates on the Account record page, using the Geolocation 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 finalize this LWC for displaying the service technician's current location, make sure…+
Before I finalize this LWC for displaying the service technician's current location, make sure it handles cases where the geolocation data might be missing or invalid for a work order. Add a fallback message or a default display, so the component doesn't break or show blank spaces.
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 an LWC to show the 'DeliveryLocation__c' (Geolocation) field from our…+
I'm trying to display a custom geolocation field from a custom object in my LWC, but it’s always showing as undefined, even though the data is present in the record.
I'm building an LWC to show the 'DeliveryLocation__c' (Geolocation) field from our 'Shipment__c' object, but it's consistently coming back as 'undefined' in the component, even though I can see the coordinates on the record. I'm afraid I'm missing a specific way to access this data type in LWC. What’s the likely diagnosis, and what’s the best next move to retrieve those coordinates correctly?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternOur developers frequently hit roadblocks trying to display non-standard field types, like…+
We often struggle to display complex custom field types like Geolocation or Rich Text in LWCs consistently, leading to frustration and inconsistent user experiences.
Our developers frequently hit roadblocks trying to display non-standard field types, like geolocation or picklist dependencies, within Lightning Web Components. This adds significant time to development and leads to inconsistent UI. What habit should we change to ensure we have a clear, reliable pattern for handling these complex field types in our LWC development?
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.