Audience:
Admin
Application:
| Application (Product) | Application Area | Release Number | Release Number |
|
Align |
CRM Integration |
17R1 - Current (24R3) |
Current (24R3) |
Question:
If a record is deleted in Veeva Align, when does its Veeva CRM counterpart also get deleted by the Integration?
Answer:
Align is designed to store, track, keep data for historical purposes - commonly referred to as Historical Data. For this reason, deleting records is not a standard option for several objects. The exception is for some Align-only objects, such as Account Rules, Projects, Footprints, which do not have CRM counterparts.
1. Records which are pushed from Align to CRM to the respective CRM objects
- territory__aln -> Territory2
- account_territory__aln -> ObjectTerritory2Association
- roster_member_territory__aln -> UserTerritory2Association
- territory_product__aln -> My_Setup_Products_vod__c
Deleting Production ("Live") Territories, Account Territories, Roster Member Territories, Territory Products in Veeva Align does not result in deleting their CRM equivalents in Veeva CRM. These records should not be deleted and should be end-dated instead to end the assignments in CRM.
If an Align record is deleted by mistake, the CRM counterpart of the data may be stuck in CRM. Removing the CRM-related data manually is the simplest option.
While it is possible to recreate the records in Align, it will not be sufficient to relink the records without recreating Integration Status 2 records.
2. Records which are imported from CRM to Align:
- Account -> account__aln
- ObjectTerritory2Association -> account_territory__aln
- Address_vod__c -> address__aln
- Child_Account_vod__c -> parent_hco__aln
- Product_vod__c -> product__aln
- Product_Group_vod__c -> product_group__aln
- Product_Metrics_vod__c -> product_metrics__aln
- Profile -> profile__aln (CRM Profile)
- PermissionSet -> permission_set__aln
- User -> roster_member__aln
- RecordType -> record_type__aln
These records should not be deleted in Align typically without specific instruction. Instead of deletion, the CRM Integration manages these records based on the CRM records' state.
- In Veeva Align, record deletion is commonly used for troubleshooting purposes, or resolving technical issues.
- Inactivation of records (through the system field status__v) should not be performed manually unless the Align Help Documentation mentions otherwise. Note: Account Rules and Targeting Rules use the Inactive and Frozen Lifecycle states to manage their status and not status__v.
Additional Resources:
Align Help Documentation:
Knowledge Base:
- What Is the Impact in Veeva Align and Veeva CRM if a Territory is End-Dated in Veeva Align?
- Is it Required to Inactivate Veeva Align Territories Once they are End Dated and Their Deletion is Pushed out to Veeva CRM? Is the status__v Field Relevant on any Other Veeva Align Objects?
- Is it Possible to Use Veeva Align and Veeva CRM in a Mixed Configuration?
- What Happens to Veeva Align Accounts Which are Deleted in Veeva CRM?
- Is Deleting the Integration Status 2 Records Safe in Veeva Align?