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.
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
- 01Store the standard and the custom forecast category as 2 named fields. Never coalesce the 2 fields.
- 02Tell the agent which field answers which question: the reps' call for the open forecast, the stage-based value for history.
- 03Count closed deals where the 2 fields disagree before any forecast-category report.