◆ Salesforce

Assign Date Field to NULL in Flow

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 taskIn the 'Update Contact Status' flow, set the 'Last Activity Date' field to null for any contact…+
In the 'Update Contact Status' flow, set the 'Last Activity Date' field to null for any contact whose 'Status' changes to 'Inactive'.
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 a contact's status changes to 'Inactive' in the 'Update Contact Status' flow, make sure…+
When a contact's status changes to 'Inactive' in the 'Update Contact Status' flow, make sure the 'Last Activity Date' field is truly cleared, not just left blank, so it accurately reflects no recent activity. I need it to be null, not an empty string, for our reporting.
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 ensure 'Last Activity Date' is truly empty for inactive contacts, but my report…+
I just ran a report on inactive contacts, and some still show a 'Last Activity Date' even after the 'Update Contact Status' flow ran.
I'm trying to ensure 'Last Activity Date' is truly empty for inactive contacts, but my report shows old dates for some. The 'Update Contact Status' flow is supposed to clear it when 'Status' becomes 'Inactive'. I'm afraid I'm not correctly setting the field to null in the flow, and I can't tell if it's a data type issue or how the flow handles empty values. What's the best way to guarantee 'Last Activity Date' is null in the flow?
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 credibility when date fields I've 'cleared' in flows still show up in reports,…+
I frequently find that date fields I intend to clear in flows are not truly null, causing inaccurate reporting.
I keep losing credibility when date fields I've 'cleared' in flows still show up in reports, making our data look messy. I need to ensure that when a date field should be empty, it's actually set to null, not just an empty string or left untouched. What habit should I change to consistently set date fields to null correctly in flows, so our reporting on empty dates is accurate?
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.