Issue 6 - Forecast category fields aren't updated Cause On the security role page, select Custom Entities tab and go to Forecast Configuration row. Select the security role for which you want to apply the privileges. Go to Advanced settings, and then select Settings > Security > Security Roles. To resolve this error, your administrator must provide read privileges on Forecast Configuration entity to your security role. There was an error in retrieving the forecast records. The error shown in the following image is displayed. You don’t have enough privileges for Forecast Configuration entity to view drill down data in the forecast grid. Issue 5 - Can't view drill down data in a forecast grid Cause Verify that the process state is Activated, and then close Settings. On the confirmation message, select Activate. Select the process, and then select Activate. You can see that the process is in the Draft state. In the search box, enter ForecastInstanceActions. Go to Advanced settings, and then select Settings > Process Center > Processes. To resolve this error, activate the ForecastInstanceActions process. The error shown in the following image is displayed.Īction (ForecastInstanceActions) for fetching forecasts has been disabled. The reason might be that the owner of an organization has changed, which is causing the failure to load the forecast grid. The ForecastInstanceActions process is deactivated. Issue 4 - Can't load the forecast grid and an error is displayed Cause For more information, see Add forecast grid and configuration options in site map. To resolve this issue, update the forecasting site map entry to the latest forecast entry grid. The following image is an example of the previous version of forecasting home page. This can be caused by the presence of an unmanaged layer of the Sales Hub app, which would allow the forecasting site map to open the previous version of forecasting. If you were using the previous version of forecasting and updated to the latest, the forecasting site map might not be updated. In the Summary section, select the Forecast category field, and then select Remove. The opportunity form opens in a new window. Open the Opportunity form of form type Main. Under Components in the solution explorer, expand Entities, expand Opportunity, and then select Forms. On the nav bar, select Settings, and then under Customization, select Customizations. The Business Management settings page opens in a new browser tab. In your app, on the nav bar, select the Settings icon, and then select Advanced Settings. To resolve this error, you must delete the Forecast category field from the form. Sometimes, the app displays the Forecast category field in opportunity forms, even after it has been configured as invisible by default through form customizations. Issue 2 - Can't hide the forecast category field in opportunity forms Cause In the Many-to-one dialog box, select the Hierarchical check box, and then select Done. On the Territory page, select the Relationships tab, and then select Parent. Select Data > Entities, and then select Territory. Select Settings > Customization > Customizations. The advance settings page opens in a tab. To resolve this issue, you must enable hierarchy in the territory_parent_territory relationship definition from Relationships. When system updates are performed, the territory entity's hierarchy is disabled (though you've enabled it earlier), which causes this error. Also, the data in a territory-based forecast might not be refreshed. When you try to create a territory-based forecast, an error is displayed. Issue 1 - An error is displayed when you try to create a territory-based forecast Symptom This article helps you troubleshoot and resolve issues related to forecasting.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |