Merge pull request #10631 from MicrosoftDocs/freshness-field-service-mobile

AB#9584: Freshness field service mobile

Author: haywoodsloan

support/dynamics-365/field-service/mobile-app/booking-timestamp-incorrect-time.md

@@ -1,10 +1,8 @@
 ---
 title: Booking timestamp is created with incorrect time
 description: Resolves the incorrect booking timestamp created when the booking status is updated in the Dynamics 365 Field Service mobile app.
-ms.author: jobaker
-author: JonBaker007
-ms.reviewer: mhart
-ms.date: 01/31/2025
+ms.reviewer: jobaker, v-wendysmith, v-shaywood
+ms.date: 01/29/2026
 ms.custom: sap:Mobile application
 ---
 # Booking timestamp is created with an incorrect time in the Field Service mobile app
@@ -19,14 +17,14 @@ On the `Booking` entity, there's an internal-use-only field called **Offline Tim
 
 Here are some ways to resolve scenarios that result in incorrect timestamps.
 
-- The **Offline Timestamp** field is missing from the booking form. In this case, it shows a form warning notification in offline mode.
+- The app shows a form warning notification in offline mode if the **Offline Timestamp** field is missing from the booking form.
 
   To solve this issue, add the **Offline Timestamp** field back to the form.
 
 - The default booking [JavaScript library on a booking form](/dynamics365/field-service/field-service-customize-scripts#form-libraries) is disabled or removed.
 
   To solve this issue, ensure the default scripts and events are enabled.
 
-- The [work order system status](/dynamics365/field-service/work-order-status-booking-status) is changed via API or a business process flow in offline mode without triggering the `OnChange` event. When the status changes to *Completed* and the work order syncs back to the server, the plug-in completes all related bookings. This process creates booking timestamps. Since the offline booking timestamp wasn't captured, the system creates the booking timestamp using the current time.
+- The [work order system status](/dynamics365/field-service/work-order-status-booking-status) changes through API or a business process flow in offline mode without triggering the `OnChange` event. When the status changes to *Completed* and the work order syncs back to the server, the plug-in completes all related bookings. This process creates booking timestamps. Since the offline booking timestamp isn't captured, the system creates the booking timestamp by using the current time.
 
-  We strongly recommend not changing the work order system status via API or a business process flow in offline mode.
+  Don't change the work order system status through API or a business process flow in offline mode.

support/dynamics-365/field-service/mobile-app/camera-picture-not-focused.md

@@ -1,10 +1,8 @@
 ---
 title: Camera pictures are blurry or not focused
 description: Improves camera quality in the Dynamics 365 Field Service mobile app on iOS devices by switching to the native iOS camera app.
-ms.author: jobaker
-author: JonBaker007
-ms.reviewer: mhart
-ms.date: 01/31/2025
+ms.reviewer: jobaker, v-wendysmith, v-shaywood
+ms.date: 01/29/2026
 ms.custom: sap:Mobile application\Issues with performance
 ---
 # Camera pictures are blurry or not focused in the Field Service mobile app

support/dynamics-365/field-service/mobile-app/duplicate-inspection-responses.md

@@ -1,10 +1,8 @@
 ---
 title: Duplicated inspection responses
 description: Reviews the audit log and offline profile filters to prevent duplicated inspection responses in Microsoft Dynamics 365 Field Service.
-ms.author: jobaker
-author: JonBaker007
-ms.reviewer: mhart
-ms.date: 01/31/2025
+ms.reviewer: jobaker, v-wendysmith, v-shaywood
+ms.date: 01/29/2026
 ms.custom: sap:Mobile application\Issues completing inspections
 ---
 # Duplicated inspection responses in Dynamics 365 Field Service
@@ -13,17 +11,17 @@ Due to the current design of the [inspection feature](/dynamics365/field-service
 
 ## Symptoms
 
-When a work order service task with an associated inspection is opened for the first time, it automatically creates an inspection response record. In some cases, the system might create a duplicate inspection response. Users might report that their answers to inspection questions are cleared. This is due to the new inspection response replacing the previous one.
+When you open a work order service task with an associated inspection for the first time, the system automatically creates an inspection response record. In some cases, the system creates a duplicate inspection response. Users might report that their answers to inspection questions are cleared. This problem happens because the new inspection response replaces the previous one.
 
 ## Resolution
 
 Administrators can review the audit log of the work order service task to check if the associated inspection response is created twice. 
 
 ### In offline scenarios
 
-The default offline profile has filters to download all work order service tasks and inspection responses. If users change the filter of the offline profile, some tasks might fail to download. Therefore, when a work order service task record is opened while the device is offline, the associated inspection response can't be found. The system assumes that an inspection response doesn't exist and creates a new one. 
+The default offline profile has filters to download all work order service tasks and inspection responses. If you change the filter of the offline profile, some tasks might fail to download. Therefore, when you open a work order service task record while the device is offline, the associated inspection response can't be found. The system assumes that an inspection response doesn't exist and creates a new one. 
 
-To resolve the issue, review the filters of your custom offline profile to download all required records. For more information, see [Configure offline capabilities](/dynamics365/field-service/mobile-power-app-system-offline).
+To resolve the issue, review the filters of your custom offline profile to download all required records. For more information, see [Configure offline capabilities](/dynamics365/field-service/mobile/set-up-offline-profile).
 
 ### With custom security roles and privileges
 
@@ -35,6 +33,6 @@ To resolve the issue, ensure that the users have permissions to access inspectio
 
 ### Using multiple devices
 
-In some scenarios, a user has two devices that can run in offline mode, and both devices have downloaded the offline data. If the user opens a work order service task on one device, and later opens the same work order service task on the other device, the system creates an inspection response record on each device. When the devices sync with the service once online, inspection responses are duplicated.
+In some scenarios, a user has two devices that run in offline mode, and both devices download the offline data. If the user opens a work order service task on one device, and later opens the same work order service task on the other device, the system creates an inspection response record on each device. When the devices sync with the service once online, inspection responses are duplicated.
 
-A similar issue may occur if the user opens the same work order service task on the web and on an offline device. Both actions create an inspection response that leads to duplicated records.
+A similar issue occurs if the user opens the same work order service task on the web and on an offline device. Both actions create an inspection response that leads to duplicated records.

support/dynamics-365/field-service/mobile-app/incorrect-missing-data-offline-mode.md

@@ -1,25 +1,23 @@
 ---
 title: Incorrect or missing data in offline mode error
 description: Resolves a common issue with missing data in the mobile offline profile in the Dynamics 365 Field Service mobile app.
-ms.author: jobaker
-author: JonBaker007
-ms.reviewer: mhart
-ms.date: 01/31/2025
+ms.reviewer: jobaker, v-wendysmith, v-shaywood
+ms.date: 01/29/2026
 ms.custom: sap:Mobile application\Offline data sync - Other
 ---
 # "Incorrect or missing data in offline mode" error
 
-This article solves a common issue with the [mobile offline profile](/dynamics365/field-service/mobile-power-app-system-offline) in the Microsoft Dynamics 365 Field Service mobile app.
+This article addresses a common issue with the mobile offline profile in the Microsoft Dynamics 365 Field Service mobile app.
 
 ## Symptoms
 
-When you use the mobile offline profile in the Dynamics 365 Field Service mobile app, the following error message might occur:
+When you use the mobile offline profile in the Dynamics 365 Field Service mobile app, you might see the following error message:
 
 > Incorrect or missing data in offline mode
 
 ## Resolution
 
-To solve this issue, review the mobile offline profile.
+To resolve this issue, review the [mobile offline profile](/dynamics365/field-service/mobile/set-up-offline-profile).
 
 > [!NOTE]
 > Before making any changes to the offline profile, create a copy to preserve the original filters.
@@ -28,4 +26,4 @@ To solve this issue, review the mobile offline profile.
 - Ensure that the offline profile is associated with the correct app module.
 - Recreate the offline profile filters in **Advanced Find** and see if they match the data you're looking for. Refine the filters if needed.
 - Verify that the proper item associations are set. If the entity in question is downloaded through an item association, check the filter of the parent item. Item associations transfer their filter to their associated entities. For example, if accounts are associated with a work order, and the work order has a custom filter that downloads only scheduled work orders, only accounts that belong to the scheduled work orders are downloaded.
-- If mobile offline is enabled for the app module, the app reads from the offline database. When the device is online, change the sync [according to the configured sync intervals](/dynamics365/field-service/mobile-power-app-system-offline#sync-intervals). You can [sync the offline database manually from the offline status page](/power-apps/mobile/offline-sync-icon).
+- If you enable mobile offline for the app module, the app reads from the offline database. When the device is online, change the sync [according to the configured sync intervals](/dynamics365/field-service/mobile/offline-data-sync#set-sync-intervals). You can [sync the offline database manually from the offline status page](/power-apps/mobile/offline-sync-icon).

support/dynamics-365/field-service/mobile-app/newux-error-on-start-missing-files.md

@@ -1,10 +1,8 @@
 ---
 title: Field Service Mobile App Can't Start Due to Missing Files
 description: Resolves Dynamics 365 Field Service mobile app launch issues due to missing source records.
-author: JonBaker007
-ms.author: jobaker
-ms.reviewer: mhart
-ms.date: 12/12/2024
+ms.reviewer: jobaker, v-wendysmith, v-shaywood
+ms.date: 01/29/2026
 ms.custom: sap:Mobile application\Application is throwing errors
 ---
 # The Field Service mobile app fails to start due to missing files
@@ -17,7 +15,7 @@ When you start using the [new user experience in the Dynamics 365 Field Service
 
 ## Cause
 
-Some required source records are missing. These records should be created when installing the Field Service app, but in rare cases, they aren't created successfully or are corrupted. It's also possible that a user deleted the records.
+Some required source records are missing. The installation process creates these records when you install the Field Service app, but in rare cases, the installation process doesn't create these records successfully or the records become corrupted. A user might also delete the records.
 
 ## Resolution
 
@@ -34,7 +32,7 @@ Some required source records are missing. These records should be created when i
    - **/card/serviceTaskGridItem.yml**
    - **/sitemaps/mobile.yml**
 
-If there's no data in the table, something went wrong with the solution update.
+If the table doesn't contain data, something went wrong with the solution update.
 
 ### Step 2: Apply the Field Service solution update again
 
@@ -50,4 +48,4 @@ If there's no data in the table, something went wrong with the solution update.
 
 1. Accept the terms of service and select **Install**.
 
-After you install the solution, verify that the table contains the required data using step 1.
+After you install the solution, verify that the table contains the required data by using step 1.

support/dynamics-365/field-service/mobile-app/newux-error-on-start-permission.md

@@ -1,10 +1,8 @@
 ---
 title: Field Service Mobile App Can't Start Due to Missing Privileges
 description: Resolves Dynamics 365 Field Service mobile app launch issues caused by missing privileges.
-author: JonBaker007
-ms.author: jobaker
-ms.reviewer: mhart
-ms.date: 12/12/2024
+ms.reviewer: jobaker, v-wendysmith, v-shaywood
+ms.date: 01/29/2026
 ms.custom: sap:Mobile Application\Application is throwing errors
 ---
 # The Field Service mobile app fails to start due to permission or privilege issues

support/dynamics-365/field-service/mobile-app/publish-mobile-offline-profile.md

@@ -1,15 +1,13 @@
 ---
 title: Troubleshoot issues with publishing a mobile offline profile
 description: Resolves common issues with publishing a mobile offline profile in the Dynamics 365 Field Service mobile app.
-ms.author: jobaker
-author: JonBaker007
-ms.reviewer: mhart
-ms.date: 01/31/2025
+ms.reviewer: jobaker, v-wendysmith, v-shaywood
+ms.date: 01/29/2026
 ms.custom: sap:Mobile application\Offline data sync - Other
 ---
 # Troubleshoot issues with publishing a mobile offline profile
 
-This article helps you solve issues with publishing a [mobile offline profile](/dynamics365/field-service/mobile-power-app-system-offline) in the Microsoft Dynamics 365 Field Service mobile app.
+This article helps you solve issues with publishing a [mobile offline profile](/dynamics365/field-service/mobile/set-up-offline-profile) in the Microsoft Dynamics 365 Field Service mobile app.
 
 ## Symptoms
 
@@ -23,7 +21,7 @@ You might receive one of the following error messages when trying to publish a m
 
 Try the following resolutions to mitigate errors while publishing an offline profile:
 
-- Count the number of linked entities and ensure the number of relationships is 10 or less. One way to do this is to view an entity's item associations and custom filters. Then, for any linked entities found, look through their item associations and custom filters to count the total number of the linked entities. Another way is to query the item associations by using `\<orgurl\>/api/data/v9.1/mobileofflineprofileitemassociations`.
+- Count the number of linked entities and ensure the number of relationships is 10 or less. One way to do this count is to view an entity's item associations and custom filters. Then, for any linked entities found, look through their item associations and custom filters to count the total number of linked entities. Another way is to query the item associations by using `\<orgurl\>/api/data/v9.1/mobileofflineprofileitemassociations`.
 
 - When the system reports a circular relationship, remove the relationship between the two reported entities from the parent entity. For example, if there's a circular relationship between *Account > Notes > Account*, and you want to download all notes related to an account record, remove the relationship to the *Notes* entity from the *Account* entity.
 

support/dynamics-365/field-service/mobile-app/settings-area-missing.md

@@ -1,10 +1,8 @@
 ---
 title: Settings Area Is Missing from the Field Service Mobile App Module
 description: Provides a resolution for the missing Settings area in the Dynamics 365 Field Service mobile app.
-author: JonBaker007
-ms.author: jobaker
-ms.reviewer: mhart
-ms.date: 12/12/2024
+ms.reviewer: jobaker, v-wendysmith, v-shaywood
+ms.date: 01/29/2026
 ms.custom: sap:Mobile application\Issues with performance
 ---
 # Settings area is missing in the Field Service Mobile app module navigation
@@ -32,7 +30,7 @@ If you find that a customization layer on the sitemap is on top and overrides th
 **Option 1**: Remove the sitemap customization layer and manually customize it again
 
 1. [Remove the unmanaged customization layer](/power-apps/maker/data-platform/solution-layers#remove-an-unmanaged-layer).
-2. Apply the [sitemap customizations](/power-apps/maker/model-driven-apps/create-site-map-app) again.
+1. Apply the [sitemap customizations](/power-apps/maker/model-driven-apps/create-site-map-app) again.
 
 **Option 2**: Manually add the **Settings** area and switch to the sitemap
 

support/dynamics-365/field-service/mobile-app/validation-restarted-background.md

@@ -1,10 +1,8 @@
 ---
 title: Validations have been restarted in the background because of inconsistent validation data error
 description: Provides a resolution for an issue where synchronous save event limitation causes an error message in Dynamics 365 Field Service forms.
-ms.author: jobaker
-author: JonBaker007
-ms.reviewer: mhart
-ms.date: 01/31/2025
+ms.reviewer: jobaker, v-wendysmith, v-shaywood
+ms.date: 01/29/2026
 ms.custom: sap:Mobile application\Can't save data
 ---
 # "Validations have been restarted in the background because of inconsistent validation data" error
@@ -13,7 +11,7 @@ This article helps resolve an issue where a synchronous save event limitation ca
 
 ## Symptoms
 
-When certain fields on a form are changed, Dynamics 365 Field Service uses the `AsyncJobTracker` pattern to retrieve and cache related records. The cached records are used for validation during the `OnSave` event. Due to a synchronous save event limitation, the system doesn't wait for asynchronous calls. The Dynamics 365 Field Service form then shows the following error message:
+When a user changes certain fields on a form, Dynamics 365 Field Service uses the `AsyncJobTracker` pattern to retrieve and cache related records. The form uses the cached records for validation during the `OnSave` event. Because of a synchronous save event limitation, the system doesn't wait for asynchronous calls. The Dynamics 365 Field Service form shows the following error message:
 
 > Validations have been restarted in the background because of inconsistent validation data. Please try again shortly.
 
@@ -23,7 +21,7 @@ Dynamics 365 Field Service has validations that require retrieving data from rel
 
 The `AsyncJobTracker` pattern is only enabled in offline mode to ensure the changed offline records are validated and can be synced back to the server.
 
-If the cached records don't match the current lookup fields, you receive the error message.
+If the cached records don't match the current lookup fields, you see the error message.
 
 ## Resolution