#Salesforce Field Service38 debatiendo

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.

@Suresh G I'd hang the public holiday on the country's operating hours, not on the big regional territory.

Field Service stores a holiday on an Operating Hours record. The service territory points at those hours, and members inherit them unless that member has different hours of their own. One EURAFRIC territory with one operating hours record means every country under it shares the same closures. A holiday in France would also block Kenya.

I'd make each country its own service territory, under the region if you still want that hierarchy. Give each country its own operating hours and add that country's public holidays there. People stay members of the countries they can actually cover. Primary can be home, and a secondary membership is how someone in the region still picks up work elsewhere.

The service appointment needs to land on the country territory. Scheduling then uses that territory's hours, so the local holiday is unavailable time. Turn on Enhanced Scheduling and Optimization, otherwise the holiday shows on the calendar and the optimizer ignores it.

Personal days are a different record. Those go on the resource's own operating hours, not on the country. If a holiday repeats every year, keep the next occurrence on those operating hours, because scheduling follows the upcoming date.

The screenshot of the message didn't come through in your post, but "It looks like there was a problem" is Lightning's generic, unhandled-error message, so the text itself doesn't tell you the root cause. Because it is intermittent, the fastest route is to capture the underlying error the next time it happens and narrow down which layer is failing. 

1. Capture the real error. When the message appears, expand the "Show details"/"More details" link if present and copy the text and error ID. Also open the browser developer console (F12 > Console/Network) before reproducing; the failing request usually shows the real exception (for example a timeout, a limit, or an Apex/Flow error). 

2. Check whether it is a platform issue. Look at

for your instance at the time of the failures and search the Known Issues site for your feature (Reports, Service Reports, Document Builder). Intermittent errors that affect several users at the same time often line up with a performance incident or a known issue. 

3. If it's a standard Salesforce report: very large or complex reports (many rows, cross filters, many groupings, formulas, long date ranges) can hit the report run-time limit or fail intermittently under load. Try adding filters to reduce the data, running it in another browser/incognito with extensions disabled, and running it as another user with the same profile. 

4. If "generating reports" means Field Service service reports or generated documents (your tags mention Generate Document): check the template for large images, many related list sections or rich-text fields, and whether the failure is tied to specific work orders/service appointments with lots of related records, line items or attachments. Also check any Flow or Apex that runs when the report/document is created (Setup > Paused and Failed Flow Interviews, Apex exception emails, debug logs for an affected user). Testing the same record with a simpler template quickly shows whether the template is the cause. 

5. If you can reproduce it with the error ID, open a case with Salesforce Support and include the error ID, timestamp, user, instance and record Id. Support can look up the error ID in their logs. 

References: 

Salesforce Known Issues:

Salesforce Trust status:

Report limits, limitations and allocations:

Field Service service reports:

Assumption: without the screenshot, error details or confirmation of whether these are standard reports or Field Service service reports/documents, this is general troubleshooting guidance rather than a confirmed root cause. If you can share the full error text and which feature you use, the community can narrow it down.