Audience:
Admin
Application:
| Application (Product) | Application Area | Release Number | Release Number |
| Align |
CRM Integration |
17R1 - Current (24R3.2) | Current (24R3.2) |
Question:
Why does extending the End Date of CRM is Deleted = True Records not work and why is this Action not recommended in Veeva Align?
Answer:
The Veeva Align objects that may falling into this scenario are:
- Territories
- Account Territories
- Roster Member Territories
- Territory Products
The CRM is Deleted field is present on these objects.
For example, when a Account Territory record is end dated, the CRM is Deleted field is set to true after a Push to CRM has been run. The true value of the field indicates that the associated CRM equivalent record (OT2A in this case) is no longer accessible in Veeva CRM.
An admin may attempt to try restoring this record by simply extending its end date. This attempt will not be successful, as as any updates done to the End Date field do not propagate to the End Datetime field of CRM is Deleted = True records nor Integration Status 2 records. New assignment records should be created instead of attempting to restore deleted records.
Additional Resources:
Align Help Documentation:
Knowledge Article:
- What is the Purpose of the CRM is Deleted Field in Veeva Align?
- How to Query Integration Status 2 Records Based on Assignment Types in Veeva Align?