Create custom fields on objects

Create custom fields on objects in Salesforce — with the four heights of help laid out: do it now, make it easier for the next person to accept, work out the right move when you are stuck, and learn the pattern so it stops coming back.

4prompt heights
Open it in the interactive atlas →

The four heights

The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.

Execute — do the immediate task

+
We need a new Annual Recurring Revenue field on the Account object for renewals reporting. Create…
We need a new Annual Recurring Revenue field on the Account object for renewals reporting. Create an Annual Recurring Revenue currency field, set precision to two decimals, default to zero, add it to the Account layout above Company Type, and make it editable only for Finance and Sales Ops profiles. Confirm the field populates on Account exports and in the Account related list on Opportunities.

Improve — make it easier to accept

+
Before I introduce a new custom currency field on Account, make it easy for teams to trust and use.…
Before I introduce a new custom currency field on Account, make it easy for teams to trust and use. Place the AR field where renewal managers will notice it, add a help text explaining calculation and owner, and ensure field-level security restricts edits to Finance and Sales Ops. Flag downstream reports and dashboards that will need updating and list any integrations that should be checked for mapping conflicts.

Decide — diagnose the stuck moment

+
I just added Annual Recurring Revenue to Account and a data import shows zeros for many records.…

I added a new currency field but imports show zeros.

I just added Annual Recurring Revenue to Account and a data import shows zeros for many records. The import template used had a column labeled ARR but the CSV values vanished. I’m worried I misconfigured the field type or mapping and will corrupt reporting. What are the likely causes, which three checks do I run in order, and how should I recover missing values while preventing the same mistake next import?

Become — change the pattern

+
Over the past year we’ve created multiple near-duplicate revenue fields across Account and…

We keep creating similar custom fields with different names.

Over the past year we’ve created multiple near-duplicate revenue fields across Account and Opportunity that confuse reporting and sales reps. I need a habit to stop field sprawl. What naming convention, approval gate, and quarterly cleanup routine should I adopt to keep the schema tidy and avoid breaking existing reports?

Next to this one

Other CRM work people do in Salesforce.

Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.

The rest of the map

Same library, five ways in.