◆ Salesforce

Deserialize JSON with reserved words in Apex

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 taskDeserialize this JSON string into an Apex object, handling the 'class' and 'new' fields…+
Deserialize this JSON string into an Apex object, handling the 'class' and 'new' fields correctly.
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 deserialize this JSON from the external system, show me the best way to handle the…+
Before I deserialize this JSON from the external system, show me the best way to handle the 'class' and 'new' fields. I need to make sure the Apex object maps correctly without syntax errors or losing data.
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 trying to deserialize a JSON string from the inventory system, but it has fields named…+
I'm trying to deserialize a JSON string that contains 'class' and 'new' as field names, and Apex is throwing errors.
I'm trying to deserialize a JSON string from the inventory system, but it has fields named 'class' and 'new'. Apex is giving me unexpected token errors when I try to parse it into a custom class. I'm afraid of breaking the data integrity. What's the best way to map these reserved word fields without changing the incoming JSON structure?
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 getting JSON from external systems that use 'class', 'new', or other reserved Apex…+
I frequently encounter JSON from external systems with reserved Apex keywords as field names, leading to repeated parsing issues.
I keep getting JSON from external systems that use 'class', 'new', or other reserved Apex keywords as field names. This always breaks my deserialization. What habit should I change to proactively handle these reserved word conflicts in my Apex custom classes, so I'm not always scrambling to fix parsing errors right before deployment?
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.