Access prerequisites before customizing a forecast DPE definition
Key Takeaway
Customize a forecast DPE definition last. First set up any new forecast fields in the forecast set, enable new source objects, and grant the access the definition needs to read source data and write results.
In Advanced Account Forecasting, the Data Processing Engine (DPE) runs definitions that calculate forecast data. When a new forecast requirement comes in, customizing a DPE definition is not the first step. A definition depends on objects that are turned on and on users who can reach the data it reads and writes. So before you change any nodes, an admin sets up the forecast side, enables any new source objects, and makes sure the right users can see the source data and write to the target fields.
Set up new forecast dimensions and metrics first
Setup on the forecast side comes before DPE changes. A new forecast dimension or metric starts as a custom field on the Advanced Account Forecast Fact object, which you then add to the forecast set.
If the requirement is a new forecast dimension...
Create a custom field on the Advanced Account Forecast Fact object. Add the field as a dimension in the forecast set. A dimension field is always a Lookup field.
If the requirement is a new forecast metric...
Create a custom Number or Currency field on the Advanced Account Forecast Fact object. Add the field as a measure in the forecast set. Do both steps before you customize the DPE definition that calculates the metric.
If a DPE definition derives the measure...
Set "Batch Process" as the calculation method for that measure in the forecast set.
A pump manufacturer wants account managers to see forecasts by distributor. Before she opens the DPE definition, the admin, Dana, creates a custom Lookup field called Distributor on the Advanced Account Forecast Fact object. She adds the field as a dimension in the forecast set. Only after that does she change the nodes in the DPE definition.