Territory Planning Patch Release Notes

Salesforce Maps v260.18

Date Pushed: April 27, 2026

The Maps package is now v260.18 and was released to sandbox on April 27, 2026

The Maps package is now v260.18 and will be released to Production Group 1 on May 4, 2026 and Production Group 2 on May 11, 2026.

Fixed an issue where the AI Optimization Summary failed to generate after running a territory plan optimization, leaving the summary section empty instead of displaying the expected AI-generated output.
Fixed an issue where filtering territory legend entries using the equals operator returned no results when the filter value contained a comma and the field was a picklist with more than 50 unique values.

Salesforce Maps v260.16

Date Pushed: April 13, 2026

The Maps package is now v260.16 and will be released to Production Group 1 on April 20, 2026 and Production Group 2 on April 27, 2026.

The Maps package is now v260.16 and was released to sandbox on April 13, 2026.

Fixed an issue that caused Assign by Logic action to time out. Known Issue

Salesforce Maps v260.13.1

Date Pushed: April 2, 2026

The Maps package is now v260.13.1 and was released to sandbox on April 2, 2026

Added the ability to view Segmentation rules in alignments.
Updated the conflict log to where it now persists in the toolbar
Added the ability to simultaneously assign and lock units to areas
Updated the look and feel of the legend
Improved bulkRunRules performance to provide more frequent conflict log updates.
Fixed an issue where manual assignments failed to apply and lock during ETM import when boundary rules were limited, causing mapping failures and backend errors.
Fixed an issue where the Territory Planning Home page failed to load due to excessive data in user preferences exceeding the remoting response size limit. Known Issue

Salesforce Maps v260.10

Date Pushed: March 23, 2026

Resolved an issue where numeric-like strings were incorrectly formatted as numbers.
Fixed a logic error in the Unique Count calculation within the Selection Summary. Known Issue
Resolved an issue where publishing territories to Enterprise Territory Management (ETM) failed when using "Account Owner" fields.
Resolved a critical performance bug where importing a specific ETM branch caused the process to run indefinitely.
Distribute top-down financial targets directly to accounts within Territory Planning. You can split targets evenly, weight them based on criteria like annual revenue, or distribute by defined segments. To ensure realistic planning, the allocation logic respects existing bottom-up targets set by the field. This alignment simplifies the transition from territory design to quota planning.

Salesforce Maps v260.6

Date Pushed: February 23, 2026

Fixed an issue where saving an area failed with an error when a record met multiple assignment rules.
Fixed an issue where publishing territories in Territory Planning as shape layers to Maps only included areas with assigned owners. Known Issue

Salesforce Maps v258.19

Date Pushed: December 23, 2025

Fixed an issue where an "invalid area center" error occurred when optimizing a live alignment.
Fixed an issue where an error occurred when you imported boundary attributes from a .csv file where an area name included a comma. Known Issue
Fixed an issue where selecting a picklist option in Territory Planning Settings didn't apply the selected option. Known Issue

Salesforce Maps v258.17

Date Pushed: December 9, 2025

Fixed an issue where you couldn't publish assignment rules to a Sales Territories parent territory when areas were split to child territories based on a large number of ZIP codes. Known Issue
Fixed an issue where point ZIP codes weren't included when publishing territories to .csv and Sales Territories. Known Issue
Fixed an issue where deleting some criteria from an assignment rule incorrectly deleted other criteria. Known Issue
Fixed an issue where publishing a territory to Sales Territories didn't also publish boundary rule. Known Issue

Salesforce Maps v258.12

Date Pushed: November 18, 2025

Couldn't search for users within a Salesforce Maps assignment rule for a territory that was published from Territory Planning to Salesforce Maps and that was missing an owner. Known Issue
An error occurred when importing a hierarchy from a Salesforce Territory Model for an alignment and the Lock Manual Assignments option was turned on. Known Issue
Assignment rules were imported incorrectly and the Run Assignment Rules action failed when importing rules from Sales Territories for a hierarchy where a rule had one or more checkbox fields turned on. Known Issue
Assignment rules weren't retained when restoring a snapshot from a territory alignment. Known Issue
An error occurred when adding a validation rule on the Territory Planning Unit Assignment object.
Duplicate nodes were created and the Import window timed out when creating an alignment from a Salesforce Territories model with over 1000 nodes or over 100 assignment rules. Known Issue
An error occurred when cloning live data alignments. Known Issue

Salesforce Maps v256.14.2

Date Pushed: September 16, 2025

Promoted the improved boundary functionality for live data from sandbox environments to production environments.

Salesforce Maps v256.13

Date Pushed: August 19, 2025

Creating territory hierarchies didn't allow planners to drag and drop areas. Known Issue

Salesforce Maps v256.11

Date Pushed: August 5, 2025

Problems with saving territory plans removed data source configurations.
Using the zoom feature on the map sometimes resulted in showing location details.

Salesforce Maps v256.10

Date Pushed: July 29, 2025

This patch didn't require updates for Territory Planning, but it did for Salesforce Maps.

Salesforce Maps v256.9

Date Pushed: July 22, 2025

This patch didn't require updates for Territory Planning, but it did for Salesforce Maps.

Salesforce Maps v256.8

Date Pushed: July 15, 2025

This patch didn't require updates for Territory Planning, but it did for Salesforce Maps.

Salesforce Maps v254.28

Date Pushed: June 10, 2025

Publishing to sales territories and selecting the option to split into child territories resulted in creating unnecessary child territories with empty rules. Known Issue
Balancing units for alignments created with live data resulted in adding postal codes to the unit counts. Known Issue
Running large reports returned non-numeric values in some instances. Known Issue

Salesforce Maps v254.26

Date Pushed: June 3, 2025

This patch didn't require updates for Territory Planning, but it did for Salesforce Maps.

Salesforce Maps v254.24

Date Pushed: May 20, 2025

When using the inline editing feature for updating top-level area owners, the affected areas disappeared from alignments. Known Issue
When using the option to limit estimates to assigned units within each area, Territory Planning incorrectly displayed an error message. Known Issue
Importing attributes failed for alignments based on live datasets when those alignments already included hierarchies and assigned units. Known Issue

Salesforce Maps v254.19

Date Pushed: April 22, 2025

Identify resolved known issues in Territory Planning since the availability of Summer '25.

Importing rules from Sales Territories for alignments with data sources from reports resulted in incomplete addresses and postal codes. Known Issue
Stamping records in Sales Planning didn't capture values for metrics other than units. Known Issue
Creating static datasets didn't save unit names correctly when using the option to import object fields. Known Issue
Creating datasets from segments didn't import details from CSV files. Known Issue
Territory Planning didn't adhere to rules imported from Sales Territories for boundaries outside the US. Known Issue
Importing CSV files for static datasets and their alignments resulted in incorrect confirmation messages stating that no records imported, even though some or all did. Known Issue
Records removed from live datasets required page refreshes to finish removing their corresponding assignments in Territory Planning. Known Issue
Assigning units to new areas didn't place selected units in the created area. Known Issue
Navigating away from and returning to the Containers section of the legend froze the screen when filtering by Is Split. Known Issue
Running assignment rules in bulk for alignments created from live datasets didn't assign units. Known Issue
Record stamping didn't reflect the record count from the live dataset. Known Issue

Salesforce Maps v252.11

Date Pushed: November 5, 2024

Fixed an issue in which address and person account fields from reports caused problems for importing rules from Sales Territories.

Salesforce Maps v250.28.1

Date Pushed: September 20, 2024

Fixed an issue that caused Territory Planning to add superfluous text when generating rules for Sales Territories.
Fixed an issue that caused scenarios to fail when using live data.
Fixed an issue that prevented importing assignment rules from Sales Territories when using data sources from Sales Planning segments.
Fixed an issue that caused the parallel processing option to duplicate unit assignments when using live data.

Salesforce Maps v250.26

Date Pushed: September 5, 2024

Added functionality for planning territories with live Salesforce data.
Fixed an issue that prevented Territory Planning from creating datasets based on the latest Salesforce data in Sales Planning segments.
Fixed an issue that prevented optimizations with calculated attributes.

Salesforce Maps v250.19

Date Pushed: July 31, 2024

Updated references to Enterprise Territory Management to its new name, Sales Territories.

Salesforce Maps v250.14

Date Pushed: July 1, 2024

This patch didn't require updates for Territory Planning, but it did for Salesforce Maps.

Salesforce Maps v248.14.2

Date Pushed: May 7, 2024

Fixed an issue that sometimes caused inconsistent results when updating records simultaneously.
Fixed an issue that prevented calculations of travel time estimates.
Added clarity to certain error messages.

Salesforce Maps v248.13

Date Pushed: April 17, 2024

This patch didn’t require updates for Territory Planning, but it did for Salesforce Maps.

Salesforce Maps v248.11

Date Pushed: April 3, 2024

This patch didn’t require updates for Territory Planning, but it did for Salesforce Maps.

Salesforce Maps v248.10

Date Pushed: March 19, 2024

This patch didn’t require updates for Territory Planning, but it did for Salesforce Maps.

Salesforce Maps v248.8

Date Pushed: February 27, 2024

Fixed an issue that prevented publishing alignments with large hierarchies to Enterprise Territory Management.

Salesforce Maps v246.10

Date Pushed: December 11, 2023

This patch didn’t require updates for Territory Planning, but it did for Salesforce Maps.

Salesforce Maps v246.9

Date Pushed: November 16, 2023

Fixed an issue that prevented creating datasets using country-level boundaries.

Salesforce Maps v246.8

Date Pushed: November 8, 2023

This patch didn’t require updates for Territory Planning, but it did for Salesforce Maps Advanced.

Salesforce Maps v246.7

Date Pushed: November 1, 2023

Improved error messages that appear when attempting to maintain fewer boundaries or geographical units than areas.
Fixed an issue that prevented boundary matching for ZIP codes.
Fixed an issue that prevented Territory Planning from flagging duplicate account IDs when creating datasets using Salesforce reports.

Salesforce Maps v244.11

Date Pushed: August 1, 2023

Fixed an issue that prevented alignments from loading with approvals enabled for high user counts.
Fixed an issue that prevented alignments from opening while using the analyze and compare feature within an outdated container set.