Merge pull request #10482 from MicrosoftDocs/freshness-field-service-dec

AB#9062: Freshness field service dec

Author: haywoodsloan

support/dynamics-365/field-service/administration/date-window-fields-missing.md

@@ -3,8 +3,8 @@ title: Date Window Start or End fields don't exist
 description: Resolves missing Date Window Start/End fields in Dynamics 365 Field Service with Time From/To Promised fields.
 author: jshotts
 ms.author: jasonshotts
-ms.reviewer: mhart
-ms.date: 09/20/2024
+ms.reviewer: v-wendysmith
+ms.date: 12/29/2025
 ms.custom: sap:Administration
 ---
 # Date Window Start/End fields don't exist in Dynamics 365 Field Service
@@ -13,10 +13,10 @@ This article discusses the missing **Date Window Start** and **Date Window End**
 
 ## Symptoms
 
-The **Date Window Start** and **Date Window End** fields are suddenly missing in Dynamics 365 Field Service.
+The **Date Window Start** and **Date Window End** fields are missing in Dynamics 365 Field Service.
 
 ## More information
 
-As of the 2021 Wave 2 update, the **Date Window Start** and **Date Window End** fields have been removed from several forms to simplify the experience. We recommend you use the **Time From Promised** and **Time To Promised** fields to define the date window in which a job should be performed.
+Starting with the 2021 Wave 2 update, Microsoft removed the **Date Window Start** and **Date Window End** fields from several forms to simplify the experience. Use the **Time From Promised** and **Time To Promised** fields to define the date window in which a job should be performed.
 
 To revert this change, see the **Pre/Post Booking Flexibility Date Field Population** setting in the [Agreements section of Field Service settings](/dynamics365/field-service/configure-default-settings#agreement-settings).  

support/dynamics-365/field-service/customization/forms-record-read-only-error.md

@@ -3,8 +3,8 @@ title: Forms show an error about being read-only
 description: Resolves the issues with read-only forms in Dynamics 365 Field Service.
 author: jshotts
 ms.author: jasonshotts
-ms.reviewer: mhart
-ms.date: 10/19/2023
+ms.reviewer: v-wendysmith
+ms.date: 12/29/2025
 ms.custom: sap:Customizations and Integrations
 ---
 # Forms show an error about being read-only in Dynamics 365 Field Service
@@ -19,6 +19,6 @@ The error message occurs in the Dynamics 365 Field Service forms:
 
 ## Resolution
 
-The Dynamics 365 Field Service makes the out-of-the-box Field Service opportunity, lead, quote, and invoice forms read-only once Field Service detects the record isn't a service-maintenance based record. Field Service forms or the forms copied from Field Service forms don't support opportunity, lead, quote, and invoice records other than Field Service opportunity, lead, quote, and invoice.
+Dynamics 365 Field Service makes the out-of-the-box Field Service opportunity, lead, quote, and invoice forms read-only when it detects the record isn't a service-maintenance based record. Field Service forms, or forms copied from Field Service forms, don't support opportunity, lead, quote, and invoice records other than Field Service opportunity, lead, quote, and invoice.
 
-To use an opportunity form for non-Field Service-related opportunities, use the out-of-the-box opportunity (**Opportunity: Opportunity**) form or create a copy of the Field Service form for further customization. The same applies for the Field Service forms for lead, quote, and invoice.
+To use an opportunity form for non-Field Service-related opportunities, use the out-of-the-box opportunity (**Opportunity: Opportunity**) form or create a copy of the Field Service form for further customization. The same guidance applies to the Field Service forms for lead, quote, and invoice.

support/dynamics-365/field-service/customization/restrict-delete-relationships.md

@@ -3,13 +3,13 @@ title: Can't delete record because of a restrict-delete relationships
 description: Provides a resolution to identify and delete related records to resolve issues with restrict-delete associations in Dynamics 365 Field Service.
 author: jshotts
 ms.author: jasonshotts
-ms.reviewer: mhart
-ms.date: 10/19/2023
+ms.reviewer: v-wendysmith
+ms.date: 01/09/2026
 ms.custom: sap:Customizations and Integrations
 ---
-# Can't delete record because of a restrict-delete relationships
+# Can't delete record because of a restrict-delete relationship
 
-This article helps resolve issues with deleting records with a *restrict-delete* association in Microsoft Dynamics 365 Field Service.
+This article helps resolve issues with deleting records that have a *restrict-delete* association in Microsoft Dynamics 365 Field Service.
 
 ## Symptoms
 
@@ -19,9 +19,9 @@ Related records with a *restrict-delete* association block the record deletion.
 
 To fix this issue, identify the relevant entities with such relationships, and then delete the records of those entities related to the record you are now trying to delete.
 
-1. Go to **Settings** > **Customizations**.
-2. Select **Customize the system**.
-3. Locate the entity with records you want to delete, such as **Accounts**.
-4. Go to **1:N Relationships** for the entity.
-5. Find any relationships where the **Type of Behavior** is *Referential, Restrict Delete*.
-6. Take note of the related entity for each of those relationships; these are the type of records that might restrict your ability to delete the record.
+1. Go to [https://make.powerapps.com/](https://make.powerapps.com/) and select **Settings** > **Advanced settings**.
+1. Select **Customizations** > **Customize the system**.
+1. Locate the entity with records you want to delete, such as **Account**.
+1. Go to **1:N Relationships** for the entity.
+1. Find any relationships where the **Type of Behavior** is *Referential, Restrict Delete*.
+1. Take note of the related entity for each of those relationships. These are the types of records that might restrict your ability to delete the record.