Loading

"Same Neighborhood" Service Objective — Field Service Summer '26 (262)

Publish Date: May 14, 2026
Description

Customers upgrading to or installing Field Service managed package version 262 (Summer '26) may notice a new Service Objective Record Type labeled "Same Neighborhood" in their org. This was introduced unintentionally and is functionally identical to the existing "Group Nearby Appointments" objective.


The correct and supported objective to use is "Group Nearby Appointments". See the Summer '26 release notes:

Help article: https://help.salesforce.com/s/articleView?id=release-notes.rn_fieldservice_262_group_nearby_objective.htm&release=262&type=5

ScenarioBehavior
Existing sandbox orgs (SB1/SB2) already upgraded to 262"Same Neighborhood" objective is active and will remain active for 262.
Existing production/sandbox orgs (R1/R2) upgrading to 262"Same Neighborhood" objective is delivered as inactive — not visible in the UI when creating a new objective.
Fresh install of 262"Same Neighborhood" objective is delivered as inactive — not visible in the UI when creating a new objective.
Fresh install of 264 (Winter '27) or later"Same Neighborhood" Record Type is not included in the package — customers will not receive it.

 

Resolution

Recommended Action

  1. Do not use the "Same Neighborhood" objective. Use the "Group Nearby Appointments" objective instead — it is the correct, supported service objective for grouping appointments in proximity.
  2. Deactivate the "Same Neighborhood" Record Type if it is active in your org:
    1. Navigate to Setup > Object Manager > Service Objective > Record Types.
    2. Locate the "Same Neighborhood" Record Type and set it to Inactive.
  3. Delete the Record Type (available from 264/Winter '27 onwards):
    1. After upgrading to package version 264 or later, the "Same Neighborhood" Record Type becomes unmanaged in your org.
    2. Administrators can then manually delete this Record Type to maintain a clean environment.
    3. Note: Upgrading to 264 will not automatically delete this record type — administrators must delete it manually.
Knowledge Article Number

005347752

 
Loading
Salesforce Help | Article