web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics 365 | Integration, Dataverse... / D365 Demand planning -...
Microsoft Dynamics 365 | Integration, Dataverse...
Suggested Answer

D365 Demand planning - Time fences versus Time freezes

(2) ShareShare
ReportReport
Posted on by SBBR-A 26
Hi, could you provide an example of how time freezes behave in the Demand Planning app? Based on my testing, I noticed that time fences display a lock icon on the generated forecast, which prevents users from editing it. However, I’m not seeing any visible effect when time freezes are configured. Even with a time freeze set up on my record, there doesn’t appear to be any change. Could you clarify how time freezes are expected to work?
 
Categories:
Dynamics 365 general
Power Platform integration
I have the same question (0)
  • Suggested answer
    DAnny3211 Profile Picture
    DAnny3211 11,417 Super User 2026 Season 1 on at

    Hello,

    Thank you for your question.

    In Dynamics 365 Demand Planning, both time fences and time freezes are used to control forecast editing and automation, but they serve slightly different purposes and behave differently in the UI.

    Time Fences:

    • Time fences typically lock forecast periods to prevent manual edits.
    • When applied, they display a lock icon on the forecast grid, clearly indicating that the forecast values are protected.
    • This is useful for stabilizing short-term forecasts that are already approved or in execution.

    Time Freezes:

    • Time freezes are intended to prevent automatic updates or recalculations of forecast values within the defined freeze period.
    • Unlike time fences, time freezes do not visually lock the forecast cells in the UI.
    • Users may still be able to manually edit values, but the system will not overwrite them during recalculation or model refresh.

    Example Use Case:

    • You might set a time fence for the next 2 weeks to prevent any changes (manual or automated).
    • You could set a time freeze for the following 4 weeks to allow manual adjustments but prevent model-driven updates.

    If you're not seeing any effect from time freezes, ensure that:

    • The freeze period is correctly configured.
    • The forecast model is set to respect freeze logic.
    • You are triggering a recalculation to observe the freeze behavior.

    Please verify if this response was helpful.
    Best regards.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Congratulations to the February Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Microsoft Dynamics 365 | Integration, Dataverse, and general topics

#1
11manish Profile Picture

11manish 166

#2
ManoVerse Profile Picture

ManoVerse 54 Super User 2026 Season 1

#3
Niki Patel Profile Picture

Niki Patel 40

Last 30 days Overall leaderboard

Featured topics

Welcome to the Microsoft Dynamics 365 forum!
Identifying an Org as CDS or Dynamics
Get batch job history log from D365 FO to Power Automate
Gross and Net Weight of Shipments feeding back into Sales Order (from External Source)

Product updates

Dynamics 365 release plans