Total Appointments Forecasted: 94,690.23 (Oct 5, 2025 - Oct 12, 2025)
What I Want to Achieve
Right now, the narrative shows the forecast period starting from this week (Sun, Oct 5) — but I want it to show next week’s forecasted count only.
For example:
This week: Oct 5 – Oct 11 → should not display
Next week: Oct 12 – Oct 18 → this should display
Basically, I want the forecast to start from the upcoming week (future period), skipping the current one.
What computation or function can I use in Quick Sight to show only next week’s forecast in my narrative or visual?
Example Goal:
Total Appointments Forecasted: 98,245.76 (Oct 12, 2025 – Oct 18, 2025)
Any guidance or example expression on how to compute or restrict the forecast window to only next week’s range would be greatly appreciated!!..
Looking back through old posts, I believe this is a current limitation with the forecasting tool in QuickSight. While dealing with the forecasting in a different visual type, the logic works the same in this scenario I believe as it does not allow you to customize the time period; it would have to be based on your current granularity that’s set and does not allow you to pick the window within your granularity that you’d like to forecast.
I’ll mark this as a feature request to promote visibility to the AWS support team.
I’d really appreciate your help with this as well.
I’m using the Forecast Insight computation in QuickSight to predict future values.
When I set the time field to “Day” and choose a period of 30, I’m getting negative forecast values.
But when I switch the time field to “Week” and set the period to 4 (which is roughly the same as 30 days), the forecast is positive and looks accurate.
Why is there such a big difference in results between the daily and weekly forecast, even though the total duration is almost the same?
Is there something about how QuickSight calculates forecasts at different time grains that causes this variation?
I assume that it has something to do with how their algorithm handles the value options within the time granularity; I can’t say for certain though as AWS does not disclose full information on how they’ve designed their forecasting tools.
This documentation provides the best background information that I can locate regarding Quick Suite’s ML forecasting features:
For example: