Troubleshooting: Settings Area Disappears in Dynamics 365 Field Service Mobile App

Table of Contents

The navigation pane within the Field Service Mobile app module is designed to provide easy access to essential functionalities. One crucial area within this navigation is the Settings area, which allows administrators to configure and customize various aspects of the mobile application experience. This article addresses a common issue where the Settings area unexpectedly disappears from the Field Service Mobile app module navigation, hindering administrators from performing necessary configurations, particularly enabling the new mobile user experience. Understanding the causes and implementing the resolutions outlined here will ensure seamless management and customization of your Field Service Mobile app.

Symptoms¶

The primary symptom of this issue is the absence of the Settings area within the Field Service Mobile app module. When administrators log into the mobile application, they find that the navigation menu lacks the expected Settings option. This missing Settings area prevents administrators from accessing critical configuration options, most notably the toggle to enable the new mobile user experience. Consequently, administrators are unable to activate and explore the latest features and improvements designed for the Field Service Mobile app, potentially impacting user experience and operational efficiency. This absence can lead to confusion and delays in deploying and managing the mobile application effectively.

Cause¶

The visibility of the Settings area in the Field Service Mobile app is governed by a combination of factors, primarily related to user permissions and sitemap configurations. The new mobile experience feature relies on a specific Settings toggle, accessible through a dedicated navigation area within the default Field Service Mobile app module. Access to this area is controlled by entity-based permissions. Users must possess write permissions on the FieldServiceSetting entity to view and interact with the Settings area. Default security roles such as System Administrator and Field Service Administrator are automatically granted these necessary permissions, ensuring that users with these roles typically have access to the Settings area without any issues.

However, the problem often arises when customizations are implemented on the sitemap of the out-of-box Field Service Mobile app module. Sitemap customizations are a powerful way to tailor the navigation experience, but they can inadvertently hide or remove default areas if not managed carefully. If a customization layer exists on the sitemap that overrides the default configuration, it may suppress the display of the Settings area. This can occur due to intentional customizations aimed at simplifying the navigation for specific user groups, or it could be an unintended consequence of broader sitemap modifications. Therefore, investigating sitemap customization layers is crucial when troubleshooting the missing Settings area issue.

Resolution¶

To restore the missing Settings area, it’s essential to investigate and potentially adjust the sitemap configurations within your Dynamics 365 environment. The resolution process involves examining the solution layers to identify any customizations that might be overriding the default sitemap settings and then taking corrective actions.

Checking Solution Layers for Sitemap Customizations¶

The first step in resolving this issue is to verify whether a customization layer is indeed the culprit. This involves examining the solution layers for the msdyn_FSMobileSettingsArea component within the fieldservice_patch_update solution. Solution layers provide a hierarchical view of how different solutions and customizations are layered on top of each other in your Dynamics 365 environment. By examining these layers, you can determine if a customization layer is overriding the default settings for the Settings area.

To check the solution layers, follow these steps:

1. Sign in to Power Apps: Begin by accessing the Power Apps maker portal. Open your web browser and navigate to https://make.powerapps.com. Log in using your Dynamics 365 administrator credentials.

2. Select Your Environment: Ensure you are working within the correct Dynamics 365 environment where you are experiencing the issue. Environments are typically listed in the top-right corner of the Power Apps portal. Select the appropriate environment from the environment switcher.

3. Open the fieldservice_patch_update Solution: Navigate to the Solutions area within the Power Apps portal. Locate and open the fieldservice_patch_update solution. This solution contains components related to Field Service Mobile app updates and patches, including the Settings area component.

4. View Solution Layers for msdyn_FSMobileSettingsArea: Within the fieldservice_patch_update solution, search for the component named msdyn_FSMobileSettingsArea. Once located, select the component and then choose the option to Show solution layers. This action will display a detailed view of the solution layers for this specific sitemap area component.

   

   By examining the solution layers, you can identify if a customization layer exists on top of the default layer for the msdyn_FSMobileSettingsArea. If a customization layer is present and is positioned above the default layer, it indicates that customizations are overriding the default sitemap configuration, potentially causing the Settings area to be hidden.

If you confirm that a customization layer is indeed overriding the default sitemap area, you have two primary options to re-enable the Settings area: removing the customization layer or manually adding the Settings area to the sitemap.

Option 1: Removing and Re-applying Sitemap Customization Layer¶

This option is suitable when the customization layer is no longer necessary or if you prefer to re-implement your customizations in a way that includes the Settings area. Removing the customization layer reverts the sitemap to the layer below it, which, if the default layer is intact, should restore the Settings area. After removing the layer, you can then manually re-apply your sitemap customizations, ensuring that the Settings area is included in the updated configuration.

Follow these steps to remove the customization layer and re-apply customizations:

1. Remove the Unmanaged Customization Layer: In the solution layers view for msdyn_FSMobileSettingsArea that you opened in the previous section, identify the unmanaged customization layer that is overriding the default layer. Select this layer and choose the option to Remove Layer. This action will remove the selected unmanaged layer, effectively reverting the sitemap configuration to the layer beneath it.

   

2. Re-apply Sitemap Customizations: After removing the customization layer, you will need to re-implement your sitemap customizations. This can be done using the sitemap editor within Power Apps. Navigate to the Apps area in Power Apps, locate and open the Field Service Mobile app for editing. Then, access the sitemap editor for this app. Carefully re-create your desired sitemap customizations, ensuring that you now explicitly include the Settings area in the navigation structure. It is crucial to test your customizations thoroughly after re-applying them to confirm that the Settings area is visible and that other functionalities are working as expected.

   

Option 2: Manually Adding the Settings Area to the Sitemap¶

If removing the entire customization layer is not feasible or desired, you can opt to manually add the Settings area back into the sitemap. This approach allows you to preserve your existing customizations while specifically re-introducing the missing Settings area. This method requires directly editing the sitemap and adding the necessary component for the Settings area.

To manually add the Settings area, perform the following steps:

1. Access the Sitemap Editor: Similar to Option 1, navigate to the Apps area in Power Apps, locate and open the Field Service Mobile app for editing. Access the sitemap editor for this app.

2. Locate the Area to Add Settings: Within the sitemap editor, identify the area where you want to insert the Settings area. Typically, it is placed within the main navigation group. Determine the logical position for the Settings area within your existing sitemap structure.

3. Add a New Subarea for Settings: In the sitemap editor, add a new Subarea component to the chosen area. Configure the properties of this new subarea to represent the Settings area. You will need to set the following key properties:

   • Title: Set the title to “Settings” or your preferred display name.
   • Icon: You can choose an appropriate icon to visually represent the Settings area.
   • Entity: Crucially, set the Entity property to FieldServiceSetting. This links the subarea to the FieldServiceSetting entity, which is essential for the Settings area functionality and permission checks.
   • ID: Assign a unique ID to the subarea, for instance, msdyn_FSMobileSettingsArea to align with the default component name, although a different unique ID will also work.

   

4. Save and Publish: After configuring the new subarea for the Settings area, save your changes within the sitemap editor and then publish the updated Field Service Mobile app. Publishing ensures that your changes are deployed and become effective for users accessing the mobile application.

After implementing either Option 1 or Option 2, it is essential to thoroughly test the Field Service Mobile app to verify that the Settings area is now visible and accessible. Log in to the mobile app as an administrator and confirm that the Settings option appears in the navigation menu. Also, test the functionality within the Settings area, including the ability to enable the new mobile user experience and other configuration options.

By systematically checking solution layers and applying one of these resolution options, you can effectively restore the missing Settings area in your Dynamics 365 Field Service Mobile app, ensuring administrators have the necessary access to configure and manage the mobile experience. Regular review of sitemap customizations and understanding solution layers will help prevent similar issues in the future and maintain a well-functioning and customizable mobile application environment.

If you have encountered this issue or have any other questions related to Dynamics 365 Field Service Mobile App sitemap customizations, please feel free to leave a comment below!