Question
Can Microsoft Dynamics 365 Business Central’s inventory forecasting and planning tools filter data by dimensions, exclude certain transactions, or use a custom start date?
Filtering And Custom Date Options Are Limited
Native Microsoft Dynamics 365 Business Central forecasting relies on sales transaction history without built-in dimension filters or transaction exclusions. Custom start dates are tied to the system work date and cannot be independently set in standard forecasting. The Enhanced Planning Pack provides extensibility, allowing filters and customizations through developer events to modify data inputs and filtering behavior. This enables organizations to extend forecasting beyond standard limitations when needed.
Native Behavior And Extensibility For Forecast Controls
Microsoft Dynamics 365 Business Central’s native forecasting pulls from historical sales data using Azure Machine Learning models, and these forecasts are generally driven by the system work date. Users cannot natively apply filters by dimensions or exclude specific transactions directly within the standard forecasting interface. This limitation exists because the forecasting engine is designed to work with continuous data for optimal prediction accuracy. As a result, users have limited control over the dataset used for forecasting within the base system.
The limitation arises because the core forecasting engine expects a continuous, unfiltered data stream to optimize demand predictions and does not expose granular transaction filtering in the user interface. To address these constraints, the Enhanced Forecasting Worksheet, part of the Enhanced Planning Pack, allows customization via published events. Developers can extend filtering capabilities to include dimensions such as shortcut dimensions or custom fields and exclude certain transaction types before the data is sent to the forecasting model. This provides a more controlled and tailored forecasting process.
Custom start dates depend on adjusting the Business Central work date temporarily during forecast runs, as direct start date overrides are not natively supported. This approach affects all date-dependent functions tied to the work date. Such extensions require developer involvement and customization but allow organizations to fine-tune forecasting inputs aligned with specific operational needs. This ensures forecasting outputs better reflect business-specific scenarios.
If historical sales data is missing or incomplete, filtering or forecast adjustments cannot function effectively. In environments without developer customization, filtering constraints and start date dependencies on work date remain unchanged. Forecasting behavior defaults to standard Microsoft Azure ML model inputs with minimal user-configurable options without extensions. Accurate and complete data remains critical for reliable forecasting results.
Extensions And Tools Related To Forecast Data Filtering
The Enhanced Forecasting Worksheet extends native forecasting by enabling developer-configurable filters across dimensions and transaction types, allowing more precise control over the input data set for demand prediction. The Enhanced Planning Pack includes this worksheet and associated tools that provide formula-based calculations of planning parameters but do not natively alter core forecasting start date logic. The Import Export PowerTool supports loading historical sales data into Business Central, enabling effective use of forecasts even if prior transaction history was absent, but does not provide runtime filtering or date customization.