You are here:
Considerations for Setting Up Einstein Forecasting
Before setting up Einstein Forecasting, review the requirements and considerations.
Required Editions
| Available in: Lightning Experience and Salesforce Classic |
| Available with Sales Cloud Einstein, which is available in Performance and Unlimited Editions, and for an extra cost in Enterprise Edition |
- Salesforce Forecasting must be enabled.
- You must work with opportunities in Salesforce for at least 12 months. Specifically, the opportunity history must show at least one update in each of the past 12 months.
- You must use a standard fiscal year. Standard fiscal years follow the Gregorian calendar, but can start on the first day of any month of the year.
- Forecasts must be measured by opportunity revenue. Predictions are generated for only the oldest activated opportunity revenue forecast type.
- Your forecast hierarchy must include at least one forecasting enabled user who reports to a forecast manager.
- You must use the standard Opportunity object and the standard Close Date and Amount fields. Custom date fields aren’t supported.
- The Amount field should be populated in at least 80 percent of open opportunities.
- Opportunity splits aren’t supported. The forecast predictions are based on total revenue, not shared revenue.
- Territories aren’t supported. Forecasts are measured by opportunity revenue, which is based on the user role hierarchy.
- To view the prediction graph on the home page when Einstein Forecasting is enabled, you must enable historical trending for Forecasting Item.
- You can use Einstein Forecasting only in production orgs, not sandboxes.
- Avoid setting field-level security on the Sales Insights Integration User Profile for opportunity fields that you want to use to optimize your predictions. It can impact your forecasting accuracy.
- If you plan to use field filters to segment your opportunities, be aware of what happens
when you delete or deactivate picklist field values.
- If you delete a picklist value from a standard field, you can’t use the value to set up a field filter.
- If you deactivate a picklist value from a standard field, you can’t use it to set up a field filter. However, existing field filters based on that value still work with opportunity records that contain the deactivated value.
- If you create a field filter using a standard field value and then delete the filtered value from the field, the filter still functions, but appears in Setup with a blank value.
- If you delete a picklist value from a custom field, it still appears in Setup, but any filter created with that value doesn’t function.
- If you deactivate a picklist value from a custom field, it can still be used to set up a field filter.
Did this article solve your issue?
Let us know so we can improve!
