Skip to main content
hamburger menu Created with Sketch.
We are currently experiencing an issue with creating new support tickets from the Help Center portal. Some users are unable to select the appropriate form when submitting their tickets. We are working to resolve the issue.

Search the Knowledge Base

How to Restore an End Dated Territory and its Related Child Data in Veeva Align?

  • Updated

Question:

How to restore an end-dated territory and its related child data in Veeva Align?

Answer:

This scenario may occur during an accidental end dating action using the Align UI or Align Dataloader.

End-dating territories is referred to as Territory closure. In turn, extending or reopening Territories means their restoration.

The process is not trivial and requires an intermediate or expert understanding of Veeva Align, data management, and data manipulation. 

If possible, recreating the territory with a different name and dataloading its child data again are the safest and easiest ways to proceed.
However, sometimes creating a new territory is not an option. The aim of this article is to explain a basic guideline of restoration of child records/assignments having standard and special sources, especially Inherited records/assignments (Created by Align or Vault triggers). 

The steps are as follows. Be sure to follow them in order:

  1. Remove all Integration Status 2 records of the territory and its related child records/assignments

    The first step is to extract and remove all IS2 records associated to the territory. This includes all Account Territory, Territory Product, Roster Member Territory, Territory IS2 records. This task can be efficiently done by using Vault Loader and VQL.

  2. Restore the Territory record itself

    The next step is about reverting the territory record itself back to its original state. Extend the end date back to the desired future date. In Business Admin or with Vault Loader, set CRM Is Deleted back to No (False).

  3. Restore the standard assignments and child records of the territory

    Account Territory assignments having the source of CRM, Align Manual, Import, MCCP (Not commonly used), and CRM Feedback can be restored by setting their CRM is Deleted to No (False) and extending their end-dates into the desired future date.

    This also applies to:

    - Territory Products having the source of Import, Align Manual.
    - Roster Member Territory records having the source of Import, Align Manual.
    - Geography Territory assignments having the source of Import, Align Manual. They do not have the CRM is Deleted field.
    - Territory Level Account Rules and Territory Level Account Exclusion records only require end-dates to be set into the future.

  4. Restore Geography Territories having the source of Footprint

    Geography Territories having the source of Footprints can be restored using the Territory Footprint records associated to the territory. Using the Align UI or Align Data Loader, the end-date of the Territory Footprint records can be extended into the future with the desired value. The end-date value of the Footprint sourced Geography Territories is restored.

  5. Restore Territory Product records having the source of Inheritance

    Territory Products having the source of Inheritance can be restored by setting their CRM is Deleted field back to No (False), and extending their end-dates to the desired future date. The connection between the Field Force Product and the Territory Product records is kept even if the Territory Products are edited in Business Admin or by Vault Loader.

  6. Restore Account Territory assignments having the source of Align Rule and/or Align Hierarchy Rule

    Be sure to restore the Geography Territory and potential Territory Level Account Assignment Rules first, before running an Assignment Preview and Commit. Running an Assignment Preview and Commit on the affected Territory recreates the Source = Align Rule / Align Hierarchy Rule Account Territory assignments. These are going to be new records entirely. The end-dated records will stay as-is. 

  7. Verify, double check the Start Date Time and End Date Time values of all of the restored records. The Start Date and End Date values have to match with their Start Date Time and End Date Time counterparts. Any updates done to the End Date field does not propagate to the End Date Time field of CRM is Deleted = True records.

  8. Push the Territory to Veeva CRM.

    As the last step, a Push can now be run on the affected territory itself to get the data changes reflected in Veeva CRM.
Notes:
  • These steps are strongly disrecommended to base standard Align Business As Usual (BAU) Activities on.
  • There may be more special cases or scenarios related to the affected territory.
  • VQL Knowledge is required. (Due to the Where Clause in the Vault Loader Tab)
  • In the event there is an MCCP associated to the territory, its end-date does not change upon end-dating the territory. This scenario is also applied when the end-dating the territory is carried out by the Vault UI or the Align Dataloader. End-dating the Territory using Business Admin and Vault Loader do not end-date child records, as no cascading occurs. 
  • MCCP related data does not get removed in CRM, even if the MCCPs, MCCP Targets are end-dated manually. The modifications are pushed out instead, such as the new end-date value of the MCCP.
  • Field Force level end dating, Either manually by the Vault UI or Align Dataloader. do not end-date any child-level records, as no cascading is happening.

Related Documentation:

Align Help Documentation:

Knowledge Article:

Powered by Zendesk