◆ Salesforce

Format DateTime for SOQL query string

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 taskI need a SOQL query string for the 'Last Modified Date' field. Format it as…+
I need a SOQL query string for the 'Last Modified Date' field. Format it as 'YYYY-MM-DDTHH:MM:SSZ' so it pulls all records from January 1, 2024, at 9 AM UTC onwards.
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 I build SOQL queries, the date-time formatting always trips me up. Make sure the 'Last…+
When I build SOQL queries, the date-time formatting always trips me up. Make sure the 'Last Modified Date' field is correctly formatted for a SOQL query string, so I don't get a 'malformed query' error again. I need it to be precise for all records after January 1, 2024, 9 AM UTC.
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 pull all records modified after January 1, 2024, 9 AM UTC for our quarterly…+
I just tried to filter a report by 'Last Modified Date' using a SOQL query, and it failed with a 'malformed query' error.
I'm trying to pull all records modified after January 1, 2024, 9 AM UTC for our quarterly review with the VP, but the query keeps failing. I'm afraid I'm missing some subtle formatting for the date-time string in SOQL, and I can't ask the dev team right now. What's the most likely issue, and how should I format 'Last Modified Date' to get this query to run correctly?
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 trying to get date-time fields formatted correctly for SOQL queries,…+
I constantly struggle with getting date-time fields correctly formatted for SOQL queries, leading to delays in reporting.
I keep losing time trying to get date-time fields formatted correctly for SOQL queries, especially when I need to specify a precise time. This often delays my ad-hoc reports for leadership. What habit should I change to consistently get the correct date-time format for SOQL query strings on the first try, so I stop getting 'malformed query' errors?
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.