25R2 Maintenance Notes
The issues listed below were fixed in 25R2. Maintenance items in the Veeva application are corrections to existing functionality.
252.3.100 (October 9, 2025)
Data Loader
|
Issue Description |
Issue Number |
|---|---|
|
Manually mapped fields on MCCP records imported via the Align Data Loader were not retained when advancing to the Preview step. |
ALN-37461 |
|
An error occurred when importing roster members via the Align Data Loader when the record was associated with a country using a deprecated timezone. |
ALN-37608 |
Territory Modeling
|
Issue Description |
Issue Number |
|---|---|
|
When a user ran a process to update a model territory's lifecycle that generated errors, the process incorrectly displayed a final status of Completed instead of Completed with Errors. |
ALN-37414 |
252.2.100 (September 11, 2025)
Map Shape Changes
| Country | State/Province | Code | Description |
|---|---|---|---|
| US | CA | 94615 | Postal point was converted to postal district |
| US | FL | 33195 | Postal point was converted to postal district |
| US | MN | 55472 | Postal point was deleted |
| US | MN | 55478 | Postal point was deleted |
| US | MN | 55554 | Postal point was deleted |
| US | MN | 55573 | Postal point was deleted |
| US | MN | 55772 | Postal point was converted to postal district |
| US | MN | 55942 | Postal point was deleted |
| US | MN | 56456 | Postal point was deleted |
| US | NJ | 08039 | Postal point was converted to postal district |
| US | NJ | 08095 | Postal point was converted to postal district |
| US | OH | 43032 | Postal point was deleted |
| US | PA | 15930 | Postal point was converted to postal district |
| US | PA | 16246 | Postal point was converted to postal district |
| US | PA | 18025 | Postal point was deleted |
| US | PA | 18448 | Postal point was deleted |
| US | PA | 19098 | Postal point was deleted |
| US | PA | 19099 | Postal point was deleted |
252.0.100 (August 7, 2025)
Account Exclusions
| Issue Description | Issue Number |
|---|---|
| When a user ran an assignment preview from a model territory, the system ignored existing Model Account Exclusions that were configured to prevent targets from being created, resulting in the preview incorrectly creating targets for accounts that should have been excluded. | ALN-36481 |
Roster Management
| Issue Description | Issue Number |
|---|---|
| When a user in CRM selected a valid timezone that was not present in the corresponding picklist in Align, the user's Roster Member record failed to import into Align. | ALN-36946 |
