A sales director wants Dynamics 365 Sales forecasting to show, alongside what reps manually submit, an AI-generated projection of revenue so leadership can compare rep judgment against a model-based estimate in the same forecast view. Which configuration should the consultant recommend?
Select an answer to reveal the explanation.
Short Explanation
What the director is actually asking for already has a home inside forecasting itself: there is a column built specifically for showing a model-generated revenue projection right next to what reps submit and their best-case numbers, so nothing needs to be bolted on from outside. The fix is just turning that column on in the forecast configuration so both numbers sit in the same view for comparison. It is tempting to think this needs a whole separate reporting tool, but that assumes native forecasting cannot do AI-driven columns, and it can, so reaching for an outside report would just be redoing work the platform already handles. Having reps type in their own AI-adjusted guess misses the point entirely, since that is still a human number, not a model output, which defeats the whole comparison the director wants. And turning on scoring elsewhere in the system does not magically populate this column on its own, the forecast still has to be told to display it. One targeted configuration change gets the director exactly what was asked for.
Full Explanation
The correct answer is D. Dynamics 365 Sales forecast configurations support adding a predicted revenue column, driven by the AI scoring engine, directly alongside the standard submitted and best-case columns, which lets leadership view rep-submitted numbers and a model-based projection side by side in a single forecast without building anything outside the platform. Option A is incorrect because it wrongly claims native forecasting has no AI support, when the predicted revenue column is a built-in configuration option; recommending a full Power BI replacement would be unnecessary extra work solving a problem that already has a native solution. Option B is incorrect because asking reps to manually type an AI-adjusted number defeats the purpose of an automated, model-generated projection and reintroduces the same subjectivity leadership is trying to compare against. Option C is incorrect because turning on predictive opportunity scoring alone does not automatically surface predicted revenue inside a forecast; the forecast configuration itself still needs to be updated to include that column before the projection appears anywhere leadership can see it. The correct path is a direct, supported configuration change to the forecast, not a separate tool or manual workaround.