To configure this feature, ensure Configuring Align is complete. Admins can configure the inbound and outbound field mappings between Align and the connected instance of Vault CRM.

Mapped Objects Between Align and Vault CRM

Field mappings can be configured for the following objects between Align and Vault CRM:

Align Object	Vault CRM Object
aln_roster_member__v	user__sys
aln_territory__v	territory__v

Fields in Align are mapped to fields in Vault CRM. Admins can view, enable, or disable standard field mappings, as well as manage custom field mappings, when needed.

To manage the list of field mappings:

1. Navigate to the Vault CRM section of the Integrations tab.
2. Select the Gear icon.
3. Select View Field Map.

4. Select the appropriate tab. The following tabs are available:

   • CRM Objects – The default selection. Field mappings in this tab represent inbound mappings.
   • Align Objects – Field mappings in this tab represent outbound field mappings
5. Select the + button next to the appropriate section to view mapped fields for that object.
6. Select Describe & Edit.

Mappings in the System Field Mapping section can be activated or deactivated, but not edited. Additionally, admins can define custom field mappings in the Custom Field Mapping section.

When saving edits to mappings in the CRM Objects tab, admins are prompted to initiate a full refresh of records of the edited object. This can be done by initiating a Full Import from CRM from the main Integrations page.

To import data from Vault CRM:

1. Navigate to the Vault CRM section of the Integrations tab.
2. Select the Gear icon.

3. Select Import from CRM to validate the credentials of the integration user. If the credentials are valid, a modal displays all objects that import into Align.

4. Select Continue.

After initiating the import, a process task is created for the import, recording the start time, end time, errors, and successes of the overall import.

Each object imported from Vault CRM has a dedicated aln_process_monitor__v record that updates with the latest date the object was imported from Vault CRM without aborting, regardless of errors occurring during the import. Each import only retrieves records added or updated since the latest date for each object.

Self Assignments

Align will import any account assignments that have originated in CRM, so that they persist. This is typically in the scenario whereby a field user in CRM has self-assigned an account.

Account Merges

When an account is merged in Vault CRM, the following process occurs:

• The account_territory__v records from the losing account get re-parented to the winning account
• The aln_account_territory__v records get re-parented to the winning account
• The losing account gets deleted

During the subsequent Import-to-Align, the following process occurs:

• If there is an overlapping manual aln_account_territory__v record with the same account__v, territory__v and source__v values on the winning account, then the winning aln_account_territory__v record has its start and end dates extended to include the lifespan of the losing aln_account_territory__v record. The losing aln_account_territory__v record gets deleted.
• All other aln_account_territory__v records that originated from the losing account persist

During subsequent rules-run in Align, the rules engine end-dates rule-sourced aln_account_territory__v records that became duplicates due to the re-parenting performed by Vault CRM.

Deleted Accounts

When an account is deleted in Vault CRM, the deleted account’s manual assignments are end dated during the subsequent Import-to-Align. During the subsequent rules-run in Align, the deleted account’s rule-based assignments are end dated.

The first time Align syncs with Vault CRM, all account_territory__v records import into Align as explicit assignments. To avoid this, users should delete all account_territory__v records from Vault CRM before syncing Align with Vault CRM for the first time.

After linking a Vault CRM instance to an Align instance, users can push records of the following Align objects to Vault CRM:

Align Object	Vault CRM Object
aln_territory__v	territory__v
aln_account_territory__v	account_territory__v
aln_roster_member__v	user_territory__v
aln_territory_product__v	my_setup_products__v

The push to Vault CRM performs the following operations:

• Create net-new records of objects in Vault CRM based on active assignments in Align
• Delete records that are past their end-date
• Update existing Vault CRM territories if the corresponding Align territories have been modified since the last push

This process only considers records modified since the last successful push to Vault CRM. Records that failed to update even though the last push was successful overall are also considered.

Operational users can initiate pushes to Vault CRM from either the Integrations page, or from an individual territory.

Pushing from the Integrations Page

Pushing from the Integrations page pushes all changes relevant to the Vault CRM instance:

1. Navigate to the Vault CRM section of the Integrations tab.
2. Select the Gear icon.
3. Select Push to CRM to validate the credentials of the integration user. If the credentials are valid, a modal displays all objects that push from Align into Vault CRM.
4. Select Continue.

Pushing at the Territory Level

Unlike pushing from the root level, pushing from a specific territory pushes only those changes associated with the selected territory and its descendants. Unrelated territories and assignments are not exported:

1. Navigate to the appropriate aln_territory__v record.

2. Select the Gear icon.

3. Select Push to CRM.

Both push processes import all new account_territory__v records into Align, regardless of which territory they apply to.

When using the User Management feature to master roster members in Align, the following behavior differences apply:

• All Roster Members mastered by Align are included in pushes to Vault CRM from the Align Integration Administration Console
• Pushing to Vault CRM from a Territory includes all Roster Members with an active Roster Member Territory assignment to that Territory or its descendants. This includes only active Roster Members that are Mastered by Align.