Merge pull request #10535 from MicrosoftDocs/main

Cloud-Writer · web-flow · commit 8d1d1a48dd2a · 2026-01-16T12:13:42.000-08:00
Auto Publish – main to live - 2026-01-16 18:00 UTC
diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json
@@ -12663,6 +12663,10 @@
       "redirect_url": "/dynamics365/field-service/deprecations-field-service#dynamics-365-field-service-integrations-with-microsoft-outlook-teams-viva-connections-and-planner---september-1-2025",
       "redirect_document_id": false
     },
+    {
+      "source_path": "support/dynamics-365/field-service/administration/attibutemap-error-upgrade.md",
+      "redirect_url": "/dynamics365/field-service/update-field-service"
+    },
     {
       "source_path": "support/dynamics-365/finance/tax/tcs-troubleshooting-failed-access-tax-service.md",
       "redirect_url": "/troubleshoot/dynamics-365/finance/welcome-finance",
diff --git a/support/azure/app-service/faqs-app-service-linux.yml b/support/azure/app-service/faqs-app-service-linux.yml
@@ -10,13 +10,7 @@ metadata:
   ms.custom: sap:Application Code Deployment   
 title: Azure App Service on Linux FAQ
 summary: |
-
-  [!INCLUDE [Feedback](../../includes/feedback.md)]
-  
-  With the release of App Service on Linux, we're working on adding features and making improvements to our platform. This article provides answers to questions that our customers have been asking us recently.
-  
-  If you have a question, comment on this article.
-  
+  This article has answers to frequently asked questions (FAQs) about App Service on Linux.  
 sections:
   - name: Built-in images
     questions:            
@@ -282,7 +276,7 @@ sections:
           You can submit your idea at the [Web Apps feedback forum](https://aka.ms/webapps-uservoice). Add "[Linux]" to the title of your idea.
           
 additionalContent: |
-  ## Next steps
+  ## Reference
   
   - [What is Azure App Service on Linux?](/azure/app-service/overview#app-service-on-linux)
   - [Set up staging environments in Azure App Service](/azure/app-service/deploy-staging-slots)
diff --git a/support/dynamics-365/field-service/administration/attibutemap-error-upgrade.md b/support/dynamics-365/field-service/administration/attibutemap-error-upgrade.md
diff --git a/support/dynamics-365/field-service/administration/cannot-find-user-set-up-frontline-workers.md b/support/dynamics-365/field-service/administration/cannot-find-user-set-up-frontline-workers.md
@@ -1,10 +1,8 @@
 ---
 title: Can't find a user when setting up frontline workers
 description: Resolves an issue where you can't find a user when trying to assign security roles in a new Field Service environment.
-author: jasonxian-msft
-ms.author: jasonxian
-ms.reviewer: v-wendysmith
-ms.date: 11/25/2024
+ms.reviewer: jacoh, v-wendysmith
+ms.date: 01/09/2026
 ms.custom: sap:Administration
 ---
 # Can't find a user when setting up frontline workers in Dynamics 365 Field Service
@@ -13,7 +11,7 @@ This article helps resolve an issue where you can't find a user when [setting up
 
 ## Symptoms
 
-When you try to [assign security roles to a user](/dynamics365/field-service/flw-admin?tabs=viva#assign-security-roles-and-field-security-profiles) when setting up frontline workers in a new Field Service environment, you can't find the user in the **Users** lookup field.
+When you try to [assign security roles to a user](/dynamics365/field-service/flw-admin?tabs=viva#assign-security-roles-and-field-security-profiles) while setting up frontline workers in a new Field Service environment, you can't find the user in the **Users** lookup field.
 
 :::image type="content" source="media/cannot-find-user-set-up-frontline-workers/users-field.png" alt-text="Screenshot of adding frontline workers in Dynamics 365 Field Service." lightbox="media/cannot-find-user-set-up-frontline-workers/users-field.png":::
 
diff --git a/support/dynamics-365/field-service/administration/cant-identify-user.md b/support/dynamics-365/field-service/administration/cant-identify-user.md
@@ -1,10 +1,8 @@
 ---
 title: Can't identify the user shown in an error message 
 description: Resolves an issue where you can't identify the user shown in an error message in Microsoft Dynamics 365 Field Service.
-author: jasonxian-msft
-ms.author: jasonxian
-ms.reviewer: v-wendysmith
-ms.date: 11/25/2024
+ms.reviewer: jacoh, v-wendysmith
+ms.date: 01/09/2026
 ms.custom: sap:Administration
 ---
 # Can't identify the user shown in an error message in Dynamics 365 Field Service
diff --git a/support/dynamics-365/field-service/administration/disable-auto-geo-code.md b/support/dynamics-365/field-service/administration/disable-auto-geo-code.md
@@ -1,8 +1,8 @@
 ---
 title: Can't create or save records due to address geocoding mapping service degradation
 description: Provides a workaround to resolve issues with saving records during service degradation of the Geo Code API in Dynamics 365 Field Service.
-ms.reviewer: mhart
-ms.date: 06/18/2024
+ms.reviewer: jasonshotts, v-wendysmith
+ms.date: 01/13/2026
 ms.custom: sap:Administration
 ---
 # Can't create or save records due to service degradation of the address geocoding mapping service
@@ -15,19 +15,19 @@ Users can't save records, such as work orders, accounts, contacts, or system use
 
 ## Cause
 
-The issue originates from a service degradation in the location APIs that the [Universal Resource Scheduling](/dynamics365/field-service/universal-resource-scheduling-for-field-service) solution uses to get the latitude and longitude information for addresses.
+The issue comes from service degradation in the location APIs that the [Universal Resource Scheduling](/dynamics365/field-service/universal-resource-scheduling-for-field-service) solution uses to get the latitude and longitude information for addresses.
 
 ## Workaround
 
 As a user, try saving the record again to ensure it's not a temporary issue.
 
 As an administrator:
 
-- To unblock operations like creating or updating records in case of a consistent failure, you can temporarily disable the [Auto Geo Code Addresses](/dynamics365/field-service/turn-on-auto-geocoding) setting in **Field Service Settings**. After re-enabling the setting, users need to manually geocode records that were updated during the outage.
+- To unblock operations like creating or updating records in case of a consistent failure, temporarily disable the [Auto Geo Code Addresses](/dynamics365/field-service/turn-on-auto-geocoding) setting in **Field Service Settings**. After re-enabling the setting, users need to manually geocode records that you updated during the outage.
 
   > [!CAUTION]
   >
-  > Disabling automatic geocoding doesn't update the geocoded information for records with updated addresses. Records might have no location information or outdated latitude and longitude values, which might affect scheduling activities that rely on location coordinates. We recommend tracking the updated records while the setting is disabled to address data gaps retroactively.
+  > Disabling automatic geocoding doesn't update the geocoded information for records with updated addresses. Records might have no location information or outdated latitude and longitude values, which might affect scheduling activities that rely on location coordinates. Track the updated records while the setting is disabled to address data gaps retroactively.
 
 - If your organization uses custom apps that call the location APIs directly from any of their processes, adjust the processes to stop calling them until the service degradation is resolved.
 
diff --git a/support/dynamics-365/field-service/administration/entity-names-duplicated-numbers.md b/support/dynamics-365/field-service/administration/entity-names-duplicated-numbers.md
@@ -1,10 +1,8 @@
 ---
 title: Entity record names have duplicate numbers
 description: Resolves issues with the incremental numbering of records for Dynamics 365 Field Service entities with auto-numbering.
-author: jshotts
-ms.author: jasonshotts
-ms.reviewer: mhart
-ms.date: 11/25/2024
+ms.reviewer: jasonshotts, v-wendysmith
+ms.date: 01/12/2026
 ms.custom: sap:Administration
 ---
 # Entity record names have duplicate numbers in Dynamics 365 Field Service
diff --git a/support/dynamics-365/field-service/administration/media/cant-identify-user/systemuser-id.png b/support/dynamics-365/field-service/administration/media/cant-identify-user/systemuser-id.png
diff --git a/support/dynamics-365/field-service/administration/user-has-no-roles.md b/support/dynamics-365/field-service/administration/user-has-no-roles.md
@@ -1,10 +1,8 @@
 ---
 title: Incorrect user privileges errors in Dynamics 365 Field Service
 description: Resolves privileges errors that occur when a user tries to access work orders in Microsoft Dynamics 365 Field Service.
-author: jasonxian-msft
-ms.author: jasonxian
-ms.reviewer: v-wendysmith
-ms.date: 11/25/2024
+ms.reviewer: jacoh, v-wendysmith
+ms.date: 01/09/2026
 ms.custom: sap:Administration
 ---
 # Incorrect user privileges errors in Dynamics 365 Field Service
@@ -28,8 +26,5 @@ When a user tries to access work orders, the following error messages appear, in
 > [!NOTE]
 > You need administrator permissions in Dynamics 365 Field Service to perform the following action.
 
-To solve this issue, [assign the correct security role and field security profile](/dynamics365/field-service/flw-admin?tabs=viva#assign-security-roles-and-field-security-profiles) to the user.
+To resolve this issue, [assign the correct security role](/dynamics365/field-service/users-licenses-permissions#assign-security-roles) and [field security profile](/dynamics365/field-service/security-permissions) to the user.
 
-## More information
-
-[Set up users, licenses, and security roles](/dynamics365/field-service/users-licenses-permissions)
diff --git a/support/dynamics-365/field-service/iot/no-device-history-properties.md b/support/dynamics-365/field-service/iot/no-device-history-properties.md
@@ -1,10 +1,8 @@
 ---
 title: No records after pulling IoT device data
 description: Resolves issues with missing data from IoT devices in Dynamics 365 Field Service by setting the Azure IoT Hub pricing and scale tier to S1-Standard.
-ms.author: vhorvath
-author: vhorvathms
-ms.reviewer: mhart
-ms.date: 11/05/2024
+ms.reviewer: vhorvath, v-wendysmith
+ms.date: 01/13/2026
 ms.custom: sap:IoT - Connected Field Service
 ---
 # No records after pulling IoT device data in Dynamics 365 Field Service
diff --git a/support/dynamics-365/field-service/iot/troubleshoot-iot-issues-logic-app.md b/support/dynamics-365/field-service/iot/troubleshoot-iot-issues-logic-app.md
@@ -1,10 +1,8 @@
 ---
 title:  Troubleshoot issues with IoT capabilities
 description: Provides a resolution to solve issues with IoT capabilities in Dynamics 365 Field Service.
-ms.author: vhorvath
-author: vhorvathms
-ms.reviewer: mhart
-ms.date: 11/05/2024
+ms.reviewer: vhorvath, v-wendysmith
+ms.date: 01/14/2026
 ms.custom: sap:IoT - Connected Field Service
 ---
 # Troubleshoot issues with IoT capabilities in Dynamics 365 Field Service
diff --git a/support/dynamics-365/field-service/rso/requirement-not-scheduled-in-rso.md b/support/dynamics-365/field-service/rso/requirement-not-scheduled-in-rso.md
@@ -1,8 +1,8 @@
 ---
 title: Requirements not scheduled in Resource Scheduling Optimization
 description: Provides a resolution to solve the issues with unscheduled requirements.
-ms.reviewer: mhart
-ms.date: 12/19/2024
+ms.reviewer: anclear, v-wendysmith
+ms.date: 01/13/2026
 ms.custom: sap:Resource Scheduling Optimization
 ---
 # Requirements not scheduled in Resource Scheduling Optimization
diff --git a/support/dynamics-365/field-service/rso/system-failed-modify-bookings-error.md b/support/dynamics-365/field-service/rso/system-failed-modify-bookings-error.md
@@ -1,8 +1,8 @@
 ---
 title: Optimization request fails to modify some bookings
 description: Resolves issues with optimization requests in the Resource Scheduling Optimization add-in for Dynamics 365 Field Service.
-ms.reviewer: mhart
-ms.date: 12/19/2024
+ms.reviewer: anclear, v-wendysmith
+ms.date: 01/13/2026
 ms.custom: sap:Resource Scheduling Optimization
 ---
 # An optimization request fails to modify some bookings
diff --git a/support/dynamics-365/field-service/scheduling/cascade-crew-changes-booking.md b/support/dynamics-365/field-service/scheduling/cascade-crew-changes-booking.md
@@ -1,10 +1,8 @@
 ---
 title: Issue with cascade crew changes when assigning a booking
 description: Resolves issues with cascade crew changes in Dynamics 365 Field Service.
-author: jshotts
-ms.author: jasonshotts
-ms.reviewer: mhart
-ms.date: 11/25/2024
+ms.reviewer: jasonshotts, v-wendysmith
+ms.date: 01/14/2026
 ms.custom: sap:Schedule Board
 ---
 # Issue with cascade crew changes when assigning a booking
@@ -21,6 +19,8 @@ This issue occurs if the value of [msdyn_CascadeCrewChanges](/common-data-model/
 
 ## Resolution
 
-To fix the issue, open the booking and set the value of `msdyn_CascadeCrewChanges` to **Yes**. Then, assign the booking to a crew again.
+1. Go to [https://make.powerapps.com/](https://make.powerapps.com/) and select your environment.
+1. Select **Tables** and open the `Bookable Resource Booking` table.
+1. Set the value of `msdyn_CascadeCrewChanges` to **Yes**. Then, assign the booking to a crew again.
 
 For more information, go to [Group resources in crews](/dynamics365/field-service/resource-crews).
diff --git a/support/dynamics-365/field-service/toc.yml b/support/dynamics-365/field-service/toc.yml
@@ -10,8 +10,6 @@
       href: administration/cant-identify-user.md
     - name: Date Window Start/End fields don't exist
       href: administration/date-window-fields-missing.md
-    - name: Error with AttributeMap when upgrading
-      href: administration/attibutemap-error-upgrade.md
     - name: Entity record names have duplicated numbers
       href: administration/entity-names-duplicated-numbers.md
     - name: Inspection flows aren't triggered 
diff --git a/support/dynamics-365/field-service/welcome-field-service.yml b/support/dynamics-365/field-service/welcome-field-service.yml
@@ -25,8 +25,6 @@ landingContent:
             url: administration/cant-identify-user.md
           - text: Date Window Start/End fields don't exist
             url: administration/date-window-fields-missing.md
-          - text: Error with AttributeMap when upgrading
-            url: administration/attibutemap-error-upgrade.md
           - text: Entity record texts have duplicated numbers
             url: administration/entity-names-duplicated-numbers.md
           - text: '"The user has not been assigned any roles" error'
diff --git a/support/dynamics/gp/version-numbers-build-numbers-of-dexterity.md b/support/dynamics/gp/version-numbers-build-numbers-of-dexterity.md
@@ -31,7 +31,7 @@ This error also occurs when you try to view a source code dictionary that is bas
 
 To resolve this problem, we recommend that you obtain a new dictionary that is based on the current build of the Dynamics.dic file. For third-party dictionaries, you can update the code that is in the current build of the Dynamics.dic file by using the Dexterity Source Code Control Service.
 
-For more information about how to upgrade a Dexterity-based application by using the Dexterity Source Code Control Service, see [How to upgrade a Dexterity-based application in Microsoft Dynamics GP by using the Dexterity Source Code Control Service](https://support.microsoft.com/topic/how-to-upgrade-a-dexterity-based-application-in-microsoft-dynamics-gp-by-using-the-dexterity-source-code-control-service-9a592921-430d-e33b-9ab5-b7072dd9d026).
+For more information about how to upgrade a Dexterity-based application by using the Dexterity Source Code Control Service, see [How to upgrade a Dexterity-based application in Microsoft Dynamics GP by using the Dexterity Source Code Control Service](./upgrade-a-dexterity-based-application.md).
 
 For dictionaries that you want to access but that you do not plan to change, follow these steps to enable the dictionaries to run in Test Mode:
 
@@ -50,4 +50,4 @@ Alternatively, you can take the following actions:
 
 ## References
 
-For more information about index files and Great Plains Dexterity source code control functionality, see [How to use an index file and the Microsoft Dynamics GP Dexterity source code control functionality to make sure that the resources that you create maintain the same resource ID in different builds and versions of your code](https://support.microsoft.com/topic/how-to-use-an-index-file-and-the-microsoft-dynamics-gp-dexterity-source-code-control-functionality-to-make-sure-that-the-resources-that-you-create-maintain-the-same-resource-id-in-different-builds-and-versions-of-your-code-02402cc4-d884-afcf-d910-1d47722c18cc).
+For more information about index files and Great Plains Dexterity source code control functionality, see [How to use an index file with Dexterity to ensure resource IDs do not change in new builds and versions](./how-to-use-index-file-with-dexterity-to-maintain-resource-ids-in-new-builds-and-versions.md).
diff --git a/support/power-platform/dataverse/environment-app-access/troubleshooting-user-needs-read-write-access-organization.md b/support/power-platform/dataverse/environment-app-access/troubleshooting-user-needs-read-write-access-organization.md
@@ -12,6 +12,8 @@ search.audienceType:
 ---
 # Troubleshoot user access issues for different environments
 
+## Summary
+
 This article helps administrators diagnose and resolve common user access issues in Power Platform environments. You'll learn how to use the built-in diagnostics tool to identify problems with permissions, licenses, security roles, and group memberships that prevent users from accessing environments and resources.
 
 To access an environment, a user must meet the following criteria:
diff --git a/support/power-platform/dataverse/working-with-solutions/missing-dependency-on-solution-import.md b/support/power-platform/dataverse/working-with-solutions/missing-dependency-on-solution-import.md
@@ -12,6 +12,8 @@ ms.custom: sap:Working with Solutions\Dependencies prevent a solution import
 ---
 # Missing dependencies error during solution import
 
+## Summary
+
 When you [import a solution](/powerapps/maker/data-platform/import-update-export-solutions) into a target environment in Microsoft Power Apps, you might encounter errors about missing dependencies. This article helps you identify the cause of missing dependency errors and provides workarounds to resolve them. It also includes best practices to help you prevent these errors in future solution imports.
 
 _Applies to:_ &nbsp; Power Platform, Solutions
diff --git a/support/power-platform/power-apps/create-and-use-apps/common-issues-and-resolutions.md b/support/power-platform/power-apps/create-and-use-apps/common-issues-and-resolutions.md
@@ -16,6 +16,8 @@ contributors:
 ---
 # Common issues and resolutions for Power Apps
 
+## Summary
+
 This article provides solutions to common problems that you might encounter when you create or use Power Apps. The article organizes problems by functional area, such as connectors, Power Automate integrations, Power Fx, and Power Apps Studio. Each section includes troubleshooting steps and links to related documentation.
 
 Before you troubleshoot specific problems, review [Power Apps troubleshooting strategies](./isolate-common-issues.md) for guidance on how to identify the source of a problem. That article outlines key principles for debugging both functional and performance problems.
diff --git a/support/power-platform/power-automate/desktop-flows/application-certificate-error.md b/support/power-platform/power-automate/desktop-flows/application-certificate-error.md
diff --git a/support/power-platform/power-automate/flow-run-issues/triggers-troubleshoot.md b/support/power-platform/power-automate/flow-run-issues/triggers-troubleshoot.md
