FindingcurrentGTM data

Two forecast-category fields: one set from stage, one reps keep

Coalescing them mixes two vocabularies, and only on closed deals.

SymptomForecast-category breakdowns show values from two different picklists, and the mix concentrates on closed opportunities.

Salesforce opportunities carry a standard forecast category, and many teams add a custom one that reps maintain. The usual read takes the custom value when present and the standard value otherwise.

The two fields speak different vocabularies. The standard one follows the stage mapping, while the custom one follows the team's forecast call. Salesforce's Opportunity object reference says ForecastCategoryName is implied by StageName and updates automatically from the stage-category mapping when the stage changes, though it can be overridden.

Reps stop maintaining the custom field after close. So the coalesced value switches vocabulary exactly on closed deals. It takes the custom value where a rep left one and the standard value where they didn't.

The affected share can be small, but all of it is closed deals, the ones forecast accuracy is judged on.

In a synthetic test set of 300 opportunities, coalescing the two fields switched 58 of 144 closed deals to the stage-based vocabulary and none of the 156 open ones. The set shows the mechanism, not how common it is.

Check your setup read-only

Compare the standard forecast category with the custom one on closed opportunities where both hold a value. If any closed deal reports a value from the other field's list, a custom-else-standard rule is mixing vocabularies.

Passes ifEvery closed opportunity your reports or agents read takes its forecast category from one field's vocabulary only.

Access needed:crm-readlocal-config

If it fails: changes to make later (not part of the check)
  1. 01Store the standard and the custom forecast category as 2 named fields. Never coalesce the 2 fields.
  2. 02Tell the agent which field answers which question: the reps' call for the open forecast, the stage-based value for history.
  3. 03Count closed deals where the 2 fields disagree before any forecast-category report.
Applies ifYour digests, routing or agents read forecast category, and your CRM has a custom forecast-category field alongside the standard one.

← Back to the stream

For your agent

Each post has a read-only check your agent can run against your own setup. Paste this into a read-only session:

Never asks your agent to change anything · send anything anywhere · fetch other pages · run code · read something you can't.

What each rule means, and how it's enforced
  • Change anything. Every check is a question answered by reading. Each one names what it reads. The steps under “If it fails” are for you to weigh later, never part of a check.
  • Send anything anywhere. No post asks an agent to email, post, submit, upload or report back. Your results stay with you; sharing them is your call.
  • Fetch other pages. Post text carries no links, and no post tells an agent to visit one. The only URLs in the feed point to this site's own post pages.
  • Run code. Snippets are illustrations, not commands.
  • Read something you can't. posts.json is generated from this page, field for field. Nothing is hidden from a human reader.

A gate enforces these rules before every publish: it refuses links, instructions aimed at an agent, write verbs inside a check, hidden Unicode characters and any check without an "access needed" line. Each published version carries a version number and a sha256 fingerprint, so you can pin the version you reviewed. Every post is reviewed by a person before it goes out.

Feed version 1.0 · 2026-11-16 · sha256 88d19978389827b7…

Found something that breaks these rules? Tell me on LinkedIn.