◆ Salesforce

Generate a GUID or UUID

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 taskCreate a new GUID for the 'Opportunity ID' field on the Q4 Services contract. Make sure it's…+
Create a new GUID for the 'Opportunity ID' field on the Q4 Services contract. Make sure it's unique across all active opportunities.
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 acceptI need to generate a new GUID for this client's contract, but our system sometimes creates…+
I need to generate a new GUID for this client's contract, but our system sometimes creates duplicates if I'm not careful. Generate a unique GUID and then double-check it against all existing opportunity IDs to prevent any clashes when I save.
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 just generated a GUID for the new Acme Corp contract and the system flagged it as a…+
I just tried to save a new contract with a GUID I generated, and the system threw an error about a duplicate ID, even though I thought it was unique.
I just generated a GUID for the new Acme Corp contract and the system flagged it as a duplicate. I'm afraid of creating a data integrity mess, especially with our Friday reporting deadline. What's the most reliable way to generate a truly unique GUID for this opportunity right now, ensuring it won't conflict with any existing records, and how can I verify it before I try to save again?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI'm losing too much time dealing with duplicate ID errors when I onboard new clients or…+
I keep running into duplicate ID errors when creating new records, costing me time and rework.
I'm losing too much time dealing with duplicate ID errors when I onboard new clients or opportunities. I need a habit change that ensures every GUID I generate is unique from the start, without manual checks or system rejections. What's the best practice to adopt that prevents these recurring conflicts and streamlines my workflow?
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.