25R2.0 Maintenance Notes
The items listed below were added in the 25R2.0 release cycle and contain maintenance items from the 25R2.0, 25R2.2, and 25R2.3 releases as they become available.
Maintenance items in the Vault CRM application are corrections to existing functionality.
252.0.10 | Family Build TBD (July 31, 2025)
Account Management
Platform |
Issue Description |
Issue Number |
---|---|---|
Browser |
When users performed bulk data loads involving Address records, they experienced long load times. |
VCRM-88151 |
Approved Notes
Platform |
Issue Description |
Issue Number |
---|---|---|
Browser |
Failure files of an Approved Notes job were labeled incorrectly. |
VCRM-57517 |
Call Reporting
Platform |
Issue Description |
Issue Number |
---|---|---|
Browser |
Users without access to the credentials__v field on the call2__v object were unable to save call reports. |
VCRM-92238 |
Browser |
When users copied Product Discussions, or when Product Discussions were copied as part of creating child call reports, values for fields marked as unique were also copied. |
VCRM-92590 VCRM-93848 |
Browser, iPad, iPhone |
When users added Product Discussions through Record Details on Unique Activities group calls, Product Discussion fields marked as unique were not hidden. |
VCRM-94111 VCRM-94112 |
Browser |
When users took an action from either the Medical Discussions or Product Discussions section of a Unique Activities call report which affected Call Objectives associated with objectives, or when they changed the account plan on the call, they were not prompted to confirm removal of the Call Objectives. |
VCRM-74156 VCRM-88538 VCRM-89413 |
Browser |
On Unique Activities parent calls, address, territory, and account plan fields in the call header were not enforced as read-only or required when they were marked as such at the layout level. |
VCRM-85303 VCRM-85309 |
Browser |
When users captured call discussions in the Product Discussions section or through the Record Details modal on Unique Activities group calls, layout-level required fields were not enforced when saving or submitting the parent call. |
VCRM-88084 |
Browser |
When Pre-Call Notes were included in a Unique Person Fields section on Unique Activities group calls, Pre-Call Notes values were not populated on child calls unless users opened the child calls before saving the call report. |
VCRM-62335 VCRM-87717 |
Browser |
When marked as read-only or required, the assign_to_comments__v and assign_to_user__v fields on the medical_inquiry_fulfillment_response__v object did not display as read-only or required on the call report. |
VCRM-64856 |
Call Sampling
Platform |
Issue Description |
Issue Number |
---|---|---|
Browser |
The appropriate fields in the Sample and Promotional Items section of the call report did not remain locked when a call with captured signatures (or a saved paper-based sampling call) was unlocked. |
VCRM-88684 |
Browser |
The Sign for Details section attribute was not enforced when users accessed detail-only call reports. |
VCRM-88683 |
Call Scheduling
Platform |
Issue Description |
Issue Number |
---|---|---|
Browser |
In My Schedule, the starting weekday did not respect the user’s configured locale. |
VCRM-90156 |
Browser |
When users’ access to an account was removed, call entries for the account no longer displayed in My Schedule. |
VCRM-93904 |
CLM
Platform |
Issue Description |
Issue Number |
---|---|---|
Browser |
An error occurred when navigating to the CLM Administration tab. |
VCRM-94824 |
Browser |
When Content Groups failed to sync from PromoMats/MedComms to Vault CRM due to an error in the external ID, the error message incorrectly referred to the record ID. |
VCRM-75282 |
Consent Capture
Platform |
Issue Description |
Issue Number |
---|---|---|
Browser |
After capturing consent from an account, the home page displayed instead of the account record. |
VCRM-89933 |
CRM Vault Metadata
Platform |
Issue Description |
Issue Number |
---|---|---|
Browser |
When mapping country fields from PromoMats/MedComms to Vault CRM, translated picklist values from the country_cda__v picklist value set were handled incorrectly. |
VCRM-95909 |
Events Management
Platform |
Issue Description |
Issue Number |
---|---|---|
Browser |
A permissions error displayed when users attempted to access the View Signatures page. |
VCRM-92632 |
Browser |
An error occurred when a user created an event when both the local time control fields and the legacy start_time_v and end_time_v fields were present on the layout. |
VCRM-79022 VCRM-71136 |
Browser |
An error occurred when attempting to unlock a closed event when the event had an associated Event Speaker record where the speaker lookup field was empty. |
VCRM-69753 |
Browser |
When a user submitted a payment expense to Concur from an event, the confirmation pop-up window displayed an incorrect button label. |
VCRM-84251 |
Browser |
When a user viewed one or more event records, the events did not display in the Recent Events list view as expected. |
VCRM-93559 |
iPad |
An error occurred when creating events when a VQL query excluded certain event types from being selected. |
VCRM-97689 |
Home Page
Platform |
Issue Description |
Issue Number |
---|---|---|
Browser |
When using multiple homepages, users were unable to add homepage widgets. |
VCRM-95162 |
MCCP
Platform |
Issue Description |
Issue Number |
---|---|---|
Browser |
When MCCP calculations ran, channel activity records were not grouped for improved performance. |
VCRM-92552 |
Browser |
An error occurred for MCCP calculation jobs due to limited disk space. |
VCRM-96504 |
Browser | When the user’s timezone was in a different day from UTC time, channel activities created on the morning of a Multichannel Cycle Plan’s start date were not included in plan calculations. | VCRM-93233 |
Medical
Platform |
Issue Description |
Issue Number |
---|---|---|
iPad |
When a user added a Documented Interest to a call while working offline, a "Required Fields Missing" error displayed in the Documented Interest text field. This error occurred even though the user had populated the field. |
VCRM-90704 |
Medical Events
Platform |
Issue Description |
Issue Number |
---|---|---|
Browser |
When a user added an attendee to a Medical Event, the newly created attendee record did not display in the Attendees related list on the event page. |
VCRM-90978 |
My Schedule
Platform |
Issue Description |
Issue Number |
---|---|---|
iPad |
In My Schedule, single-day external calendar events with a duration greater than 16 hours displayed as all-day events. |
VCRM-89692 |
Browser |
When users scheduled a call or applied call cycles for an account with multiple territory records using the same address, a duplication error message displayed. |
VCRM-96197 |
Network Integration
Platform |
Issue Description |
Issue Number |
---|---|---|
iPad |
When users attempted to create an account, the country values did not display for a CRM Object Reference field mapped to the primary_country__v field. This prevented users from creating the Account. |
VCRM-90333 |
Nitro
Platform |
Issue Description |
Issue Number |
---|---|---|
Browser |
When a user performed a Nitro data sync, the process failed for a specific Nitro data table when the size of the data returned for that query exceeded the system's 10 MB response buffer limit. The user's device displayed zero records for the affected table. |
VCRM-95477 |
Order Management
Platform |
Issue Description |
Issue Number |
---|---|---|
Browser |
When a user attempted to run a report with a specific date range filter, the filter was ignored. The resulting report incorrectly included all records from the database instead of only those within the specified dates. |
VCRM-91190 |
Service Center
Platform |
Issue Description |
Issue Number |
---|---|---|
Browser |
When a user attempted to create a target list without the required permissions, the system displayed an error dialog box that was missing the specific error message text. |
VCRM-95137 |
Sync
Platform |
Issue Description |
Issue Number |
---|---|---|
iPad |
After users synced a large number of account_territory__v records, including records for territories they were not assigned to, updating the VMOC WHERE clause and performing an incremental sync did not remove the records filtered out by the WHERE clause. To remove unwanted account_territory__v records, admins must enable enhanced sync for the account_territory__v VMOC and end users must perform an incremental sync. Admins should disable enhanced sync once the records are removed. |
VCRM-93333 |
Browser |
An error occurred when duplicate application labels were created for Veeva Messages. |
VCRM-91272 |
iPad |
An error occurred when users did not have the permissions to delete records created by the System. |
VCRM-94080 |
Browser |
When the syncoffline__v field was added to a base document type, a sync error occurred. |
VCRM-93393 |
Territory Management
Platform |
Issue Description |
Issue Number |
---|---|---|
Browser |
The Territory Specific Fields (TSF) processor job failed intermittently. |
VCRM-92628 |
X-Pages
Platform |
Issue Description |
Issue Number |
---|---|---|
Browser |
When a user selected a viewSection() link on an X-Page using Browser, the navigation failed with an internal server error. While the link worked correctly on iPad, it did not work online because the target studio_id__v existed on two different HTML Report records, causing a "Duplicate key" error during the lookup process. |
VCRM-90397 |
Browser |
When a user tried to add a Patient Pathway or its steps from an X-Pages dashboard, the action failed because the country__v field on the Patient Journey object was changed to a required field in Vault CRM, preventing the X-Page from creating or updating the record as it had previously in Veeva CRM. |
VCRM-97891 |
X-Pages Studio
Platform |
Issue Description |
Issue Number |
---|---|---|
Browser |
The data displayed on a deployed page on an iPad was different from the data displayed in the X-Pages Studio preview. Studio preview interpreted empty string values from a query as Null, whereas the iPad platform interpreted the same values as an empty string (""). |
VCRM-89498 |
Browser |
When a user saved a new version of an X-Page, the system indicated the version was deployable, but the new version was not available for selection when creating or editing a deployment. This occurred for multiple pages that used the same Custom Display Element (CDE). |
VCRM-91429 |
Browser |
When a user configured date calculations in X-Pages Studio, the system returned incorrect values. The "End of Calendar Period" function for a week returned the day before the input date instead of the proper end of the week. Additionally, the "Beginning of Calendar Period" function for a week did not respect the user's locale settings, incorrectly using Sunday as the start of the week. |
VCRM-92053 |