Consumption Forecasting known limitations article

Important Requirement — Forecast Manager Must Be Assigned in the Role Hierarchy

This is the most common reason Consumption Forecasting does not work. A Forecast Manager must be assigned in your role hierarchy before Consumption Forecasting will function. Please review your hierarchy setup before troubleshooting other areas.
What you may see if a Forecast Manager is missing:

• The Forecasts tab displays: "We couldn't display the forecast data. Refresh the page and try again."
• Forecast rollups work for some managers but not others
• Users appear in the hierarchy but their data does not aggregate upward

Steps to resolve:

1. Go to Setup → Forecasts Settings → Forecast Hierarchy
2. Confirm that at least one user is assigned as a Forecast Manager at the top of the hierarchy
3. Ensure every user who needs to view or contribute to forecasts is placed in the role hierarchy and has a Forecast Manager assigned above them
4. Verify the Allow Forecasting permission is enabled on the user's Profile or Permission Set
5. See Assign the Forecast Manager Role in Salesforce Help for step-by-step instructions

Additional notes:

• Territory-based hierarchies are not supported — Consumption Forecasting requires a role-based hierarchy
• If your org has a flat role structure or no role hierarchy, you must create roles before enabling Consumption Forecasting
• Admins at the top of the role hierarchy who are not assigned a role will not appear as Forecast Managers and will not be able to view forecasts unless they have the View All Forecasts permission

Important Limitation — Consumption Forecasting Cannot Be Disabled After Enabling

Please be aware: Once Consumption Forecasting is enabled in your org, it cannot be turned off through Setup. If you need to disable it, you will need to contact Salesforce Support to request a back-end configuration change. We strongly recommend testing in a Sandbox environment before enabling in Production.
What you will see after enabling:

• The option to disable Consumption Forecasting in Setup will be unavailable (greyed out)

If you need to disable Consumption Forecasting:

• Contact Salesforce Support and request that Consumption Forecasting be disabled for your org
• Test all configuration changes in a Sandbox before applying them to Production

Data Model Object (DMO) Setup & Data Cloud Configuration

DMOs must be mapped before they can be used in Consumption Forecasting:

• DMOs must appear in the mapped DMO list view within Data Cloud before they can be selected during Consumption Forecasting configuration
• If a DMO does not appear as an available option, it must be mapped in Data Cloud first
• Navigate to Data Cloud → Data Model to map your DMOs

Note about Transformation DMOs:
Consumption Forecasting requires that every DMO used in a Forecast Type includes a Name__c field. If this field is missing, the forecast grid will fail to load for managers with a 400 BAD_REQUEST error referencing an "unknown column" — even though individual contributor data may appear correctly. This is a known limitation that applies specifically to Transformation DMOs.
Important: Transformation DMOs are not required to be mapped in the standard Data Cloud mapped DMO list view, but they must include a Name__c field in their schema for Consumption Forecasting rollups to function. 
Symptoms of a missing Name__c field:

• The Forecasts tab displays: "We couldn't display the forecast data. Refresh the page and try again."
• Individual contributors can view their own forecast data, but manager-level rollups fail
• Recreating the Consumption Forecast Type with fresh DMOs does not resolve the issue
• The error persists across both Sandbox and Production orgs using the same DMO structure

Steps to resolve:

1. Review each DMO used in your Consumption Forecast Type and confirm that a Name__c column is present in the DMO schema
2. If Name__c is missing, use a data transform in Data Cloud to populate a Name__c column with the appropriate display value (for example, the account or product name field)
3. Once Name__c is populated, recreate or re-save the affected Consumption Forecast Type
4. Verify that the Data Governance tab is visible to the user testing the forecast — by default, this tab is hidden for System Administrator profiles and must be explicitly enabled

Note on the Data Governance tab:

• The Data Governance tab is hidden for System Administrator profiles by default
• If you cannot see the tab, follow the steps in Enable Data Governance Permissions for Consumption Forecasting Objects to make it visible
• Ensure the default All Data Access Ruleset is in place before troubleshooting further

If you are experiencing DMO-related errors:

• Try recreating the Consumption Forecast Type using freshly mapped DMOs — this has been known to resolve certain rollup and display errors

Features Not Supported with Consumption Forecasting

The following standard forecasting features are not available when using Consumption Forecasting:

• Forecast Submissions
• Adjustments and Judgments
• Manage Forecast Rollups
• Territory Hierarchy (role-based hierarchy only)
• More than three rollup levels (User → 2 additional business dimensions)
• Manual forecast editing by sellers
• Forecast submission and approval workflows

Rollup Issues Affecting Some Managers

If forecast rollups are working for some managers but not others, work through these steps:

1. Verify each affected user is placed in the correct forecast hierarchy node for the Consumption Forecast Type
2. Confirm the user has the Allow Forecasting permission enabled
3. Check that the user has a Forecast Manager assigned in their role hierarchy
4. Review the Consumption Forecast Type configuration and confirm the correct measure field is selected
5. If the issue persists, try creating a new Consumption Forecast Type as a workaround

"Something Went Wrong" or "Couldn't Display Forecast Data" Errors

These errors typically trace back to one of the following:

1. No active Forecast Type — Go to Setup → Forecasts Settings and confirm at least one Forecast Type is set to Active
2. Missing Forecast Manager — The affected user, or their manager, does not have a Forecast Manager assigned in the hierarchy
3. Data Cloud misconfiguration — DMOs are not mapped or the Data Cloud connection to Sales Cloud is not active
4. Missing permissions — The Allow Forecasting permission or Data Governance permissions are not enabled for the user
5. Fiscal year configuration — Custom fiscal years that are incompletely configured can cause errors on the Forecasts tab