24R3 Maintenance Notes
The issues listed below were fixed in 24R3. Maintenance items in the Veeva application are corrections to existing functionality.
243.5.40 (April 3, 2025)
Vault CRM Integration
|
Issue Description |
Issue Number |
|---|---|
|
When new Content Groups and members were pushed from Align to Vault CRM, resulting in a new Content Group being generated in Vault CRM, subsequent pushes of assignments from Align overrode the assignments to the CRM-generated Content Group. |
VALN-4033 |
|
Pushes to Vault CRM failed when Number fields were mapped on the roster_member__aln object. |
VALN-4038 |
243.5.10 (March 13, 2025)
Vault CRM Integration
|
Issue Description |
Issue Number |
|---|---|
|
Content Groups removed in Align were not deleted in Vault CRM after pushing. |
VALN-1921 |
|
An error occurred when an Import to CRM job took a long time to complete. |
VALN-3551 |
|
integration_status_2__aln records did not correctly regenerate when deleted, causing integration errors. |
VALN-3740 |
243.4.40 (March 6, 2025)
Vault CRM Integration
|
Issue Description |
Issue Number |
|---|---|
|
An error occurred when upserting many records into Vault CRM Align, causing some records to associate incorrectly. |
VALN-3846 |
243.4.10 (February 13, 2025)
Data Loader
|
Issue Description |
Issue Number |
|---|---|
|
Using the Vault Loader to upsert into existing roster_member__aln records overrode the value in the enable_ms_outlook_calendar__aln field. |
VALN-2861 |
243.2.10 (January 9, 2025)
Vault CRM Integration
|
Issue Description |
Issue Number |
|---|---|
|
Importing from Vault CRM failed when an empty user__sys picklist in Vault CRM was mapped to a non-empty roster_member__aln picklist. |
VALN-2930 |
243.0.10 (December 5, 2024)
Integrated Territory Feedback
|
Issue Description |
Issue Number |
|---|---|
|
Model account exclusion records created via a Remove Account challenge did not populate the country__aln field during automated feedback processing. |
VALN-2058 |
Roster Management
|
Issue Description |
Issue Number |
|---|---|
|
Roster members could not have a crm_user_status__aln of Active with an end_date__aln field in the past. |
VALN-813 |
|
The crm_security_policy_override__aln, crm_application_profile_override__aln, and crm_layout_profile_override__aln fields on the roster_member__aln object did not function correctly without being mapped as part of the custom roster_member__aln outbound field mapping. |
VALN-2029 |
|
A scripting error caused some roster_member__aln fields to not import from CRM if designated as a CRM-managed field. |
VALN-2028 |
|
A scripting error caused some roster_member__aln fields to not push to CRM if designated as a CRM-managed field. |
VALN-1344 |
Vault CRM Integration
|
Issue Description |
Issue Number |
|---|---|
|
In certain scenarios, integration_status_2__aln records were processed incorrectly when pushing multiple roster_member_territory__aln and territory_product__aln assignments to Vault CRM for invalid user records. |
VALN-2039 |
