#FSL Mobile2 人正在讨论

Yes, you can customize the fields shown on Service Appointment list views in the Salesforce Field Service mobile app, but the configuration relies on field sets rather than standard compact layouts. The fields displayed on the service appointment cards within the mobile schedule view are explicitly controlled by a field set named Service Appointments List Columns. To change these fields, navigate to the Object Manager in Salesforce Setup, select the Service Appointment object, open the Field Sets section, and edit this specific field set to add, remove, or rearrange your desired fields. Because mobile screen real estate is limited, only the first few fields in the field set will display on the card before the remaining data is truncated. 

While the field set dictates which fields are visible on the mobile card, the actual criteria for which records appear are controlled by standard Salesforce list view filters. The mobile application maps to these criteria using the developer name of the list view, which must be referenced in your Field Service Mobile Settings under the default list view parameter. This separates the record filtering logic from the physical layout of the fields. After saving your changes in Setup, mobile users must perform a pull-to-refresh on their schedule view, clear cached data in their app settings, or log out and log back in to force a metadata synchronization and see the updated fields.

In a Profile or Permission Set make sure to check the "Use Order Management Return Order" system permission to be able to access Return Order Object.

This is a poorly documented behavior of Return Order object that is counter-intuitive to troubleshoot as without this permission OWD and CRUD settings are ignored.

Hope this helps!

Hi @Rei Suzuki

Hope you are doing well

The standard__webPage type in NavigationMixin should indeed work for opening web pages in Salesforce Mobile. However, there might be issues with the URL format or the structure of your code causing errors.

Here's an example of how you should structure the code:

.....................................................................................................

import { LightningElement } from 'lwc';

import { NavigationMixin } from 'lightning/navigation';

export default class YourComponent extends NavigationMixin(LightningElement) {

    openFileUrl = 'https://example.com/library/My Documents/MyPage.aspx?id=%2FMy%20Documents%2F0WO01000001jrM3GAI/IMG_0111.jpeg';

    navigateToURL() {

        this[NavigationMixin.Navigate]({

            type: 'standard__webPage',

            attributes: {

                url: this.openFileUrl

            }

        });

    }

}

..............................................................................................................................................

A few things to consider:

1. Ensure that your URL is properly encoded. It seems like the URL you provided might have an issue with the encoding (e.g., spaces should be replaced with %20). Ensure that special characters are appropriately URL encoded.
2. Check the permissions and settings within Salesforce Mobile. Sometimes, if the URL is considered unsafe or blocked, it might cause an error.
3. Verify that the code structure and import statements are correct in your Lightning Web Component (LWC). Ensure that the component is correctly wired up to the button or action that triggers this navigation.

1. Hope you will understand your issue with this content.

1. Thanks!

1. #FSL Mobile #Service Cloud