You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -3,18 +3,17 @@ title: Troubleshoot issues with forecasting
3
3
description: Provides resolutions for the known issues that are related to forecasting in Dynamics 365 Sales.
4
4
author: sbmjais
5
5
ms.author: shjais
6
-
ms.topic: troubleshooting
7
-
ms.date: 02/28/2022
6
+
ms.reviewer: ladirohit
7
+
ms.date: 09/06/2023
8
8
ms.subservice: d365-sales-sales
9
9
---
10
-
11
10
# Troubleshoot issues with forecasting
12
11
13
-
This article helps you troubleshoot and resolve issues related to forecasting.
12
+
This article helps you troubleshoot and resolve issues related to forecasting in Microsoft Dynamics 365 Sales.
14
13
15
14
## Issue 1 - An error is displayed when you try to create a territory-based forecast
16
15
17
-
### Symptom
16
+
### Symptoms
18
17
19
18
When you try to create a territory-based forecast, an error is displayed. Also, the data in a territory-based forecast might not be refreshed.
20
19
@@ -149,20 +148,125 @@ To resolve this error, your administrator must provide read privileges on **Fore
149
148
150
149
### Cause
151
150
152
-
In a forecast, after updating the forecast category field to Won or Lost, the opportunities are still appearing in the previous pipeline bucket. This error is occurring due to the **Opportunity Forecast Category Mapping Process** workflow is disabled in your organization.
151
+
In a forecast, after updating the forecast category field to **Won** or **Lost**, the opportunities still appear in the previous pipeline bucket. This error occurs because the **Opportunity Forecast Category Mapping Process** workflow is disabled in your organization.
153
152
154
153
### Resolution
155
154
156
155
To resolve the error, activate the **Opportunity Forecast Category Mapping Process** workflow. Follow these steps:
157
156
158
157
1. Go to **Advanced settings**, and then select **Settings** > **Customizations** > **Customize the System**.
159
-
2. From the sitemap, select **Processes**.
160
-
3. Select the **Opportunity Forecast Category Mapping Process** workflow and select **Activate**.
158
+
1. In the sitemap, select **Processes**.
159
+
1. Select the **Opportunity Forecast Category Mapping Process** workflow and then select **Activate**.
160
+
161
+
:::image type="content" source="media/troubleshoot-forecast-issues/activate-opportunity-forecast-category-process.png" alt-text="Activate the Opportunity Forecast Category Mapping Process workflow.":::
162
+
163
+
The forecast categories in the opportunities will be updated properly. The opportunities that were changed before activating the workflow must be manually changed. Also, open the **Opportunity Forecast Category Mapping Process** workflow and verify that the conditions are properly defined for each forecast category.
## Issue 7 - Can't activate a forecast that has a hierarchy-related column of lookup type
170
+
171
+
### Cause
172
+
173
+
This issue occurs because the "Dynamics 365 Sales Forecasting" user doesn't have the read permission to the hierarchy-related lookup entity.
174
+
175
+
### Resolution
176
+
177
+
To solve the issue, follow the steps:
178
+
179
+
1. Go to **Advanced settings**, and select **Settings** > **System** > **Security** > **Security roles**.
180
+
181
+
1. Open the **Forecast AppUser** role and select the tab where the entity type is present.
182
+
183
+
:::image type="content" source="media/troubleshoot-forecast-issues/set-up-read-permission.png" alt-text="Screenshot that shows the the Forecast App User role.":::
184
+
185
+
1. Enable the **Read** permission at the organization level for the lookup field's entity type.
186
+
1. Save the changes.
187
+
188
+
## Issue 8 - Can't activate a forecast
189
+
190
+
### Cause
191
+
192
+
The forecast activation fails due to multiple reasons.
193
+
194
+
### Resolution
195
+
196
+
To solve the issue, follow the steps:
197
+
198
+
1. Ensure that you have done all the mandatory configurations for your forecast model.
199
+
1. Ensure that hierarchy filters in the forecast configuration don't filter out the entire hierarchy. Go to the **Preview** section in the **General** step to ensure that the hierarchy exists. For more information, see [Add additional filters to a forecast](/dynamics365/sales/add-additional-filters).
200
+
201
+
## Issue 9 - Can't find the forecast configuration option in App Settings
202
+
203
+
### Cause
204
+
205
+
The forecast configuration option might not be visible in the App Settings of the Sales Hub app due to the following reasons:
206
+
207
+
- You don't have the read permission to the forecast configuration entity.
208
+
- Your administrator didn't manually [add the forecast grid and configuration](/dynamics365/sales/add-forecast-site-map#add-forecast-grid-and-forecast-configuration-options-to-sitemap) under the **Performance Management** section.
209
+
210
+
### Resolution
211
+
212
+
To solve the issue, follow these steps:
161
213
162
-
:::image type="content" source="media/troubleshoot-forecast-issues/activate-opportunity-forecast-category-process.png" alt-text="Activate the Opportunity Forecast Category Mapping Process workflow.":::
214
+
1. Assign the Forecast Manager security role to the user who should be able to create and manage forecast configurations.
215
+
1. In **Forecast configuration**, the forecast navigation pane items must be added in a custom app.
163
216
164
-
The forecast categories in the opportunities will be updated properly. For opportunities that were changed before activating the workflow must be manually changed. Also, open the **Opportunity Forecast Category Mapping Process** workflow and verify that the conditions are properly defined for each forecast category.
217
+
## Issue 10 - Can't view forecasts for user hierarchy
This issue occurs due to insufficient permissions to view the forecast.
222
+
223
+
### Resolution
224
+
225
+
To solve the issue, make sure that:
226
+
227
+
1. One of these conditions is satisfied:
228
+
229
+
- You're the owner of the forecast. The **Owner lookup field** in the **Permissions** step of the forecast configuration shows who the owner is.
230
+
231
+
:::image type="content" source="media/troubleshoot-forecast-issues/permission.png" alt-text="Screenshot that shows the Permissions step of the forecast configuration.":::
232
+
233
+
- You're part of the security roles that have the read permission, as configured in the **Permissions** step of the forecast configuration.
234
+
- Someone has shared the forecast with you. For more information, see [Enable or disable forecast sharing](/dynamics365/sales/provide-permissions-forecast).
235
+
236
+
1. The **Owner lookup field** in the **Permissions** step of the forecast configuration isn't set to **None**. If it's set to **None**, no one can view the forecast.
237
+
238
+
## Issue 11 - Forecast field values show zero or blank in the forecast grid
239
+
240
+
### Cause
241
+
242
+
The fields in the rollup entity have field-level security.
243
+
244
+
### Resolution
245
+
246
+
To solve the issue, you need to provide the read permission to the Dynamics 365 Sales Forecasting user in the field security profiles. Otherwise, the column will show **0** to all users except system administrators. Follow these steps to configure the field security profiles:
247
+
248
+
1. Go to **Settings**> **Security** > **Field Security Profiles**.
249
+
1. Select an existing profile or create a new one.
250
+
1. Select **Users** or **Teams** to add the users or teams that you want to grant access to the secure fields.
251
+
1. Select **Field Permissions** to set the permissions for each field. You can select **Read**, **Create**, or **Update**, or a combination of them.
252
+
1. Save and close the profile.
253
+
254
+
## Issue 12 - Can't manually recalculate the prediction column on the Forecasts page
255
+
256
+
### Cause
257
+
258
+
The prediction column on the **Forecasts** page can't be [manually recalculated](/dynamics365/sales/keep-forecast-data-up-to-date#recalculate-and-refresh-forecast-data-manually).
259
+
260
+
### Resolution
261
+
262
+
The prediction column in the Forecast is automatically recalculated after every seven days, and it doesn't support manual recalculation. This is because predictions are based on AI-driven models that look at historical data and the open sales pipeline to predict future revenue outcome. The prediction column shows the predicted revenue for each seller and manager based on the **Status** field of an opportunity. To optimize the accuracy of the predictions, ensure the **Forecast Category** values are kept in sync with the **Status** field. For the out-of-the-box forecast category, a workflow ensures that when an opportunity is closed as **Won** or **Lost**, the forecast category is updated with the proper value.
263
+
264
+
## Issue 13 - Forecast underlying grid view is disabled (read-only) when the page is loading
265
+
266
+
### Cause
267
+
268
+
A [custom JavaScript configured in the forecast configuration](/dynamics365/sales/forecast-configure-advanced-settings#upload-the-javascript-library-to-your-forecast) prevents the grid from being editable.
269
+
270
+
### Resolution
167
271
168
-
4. Save and close the settings.
272
+
To solve the issue, review the custom JavaScript code and check if it disables the underlying records grid view.
0 commit comments