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

The following objects are mapped between Align and Vault CRM:

Align Object	Vault CRM Object
aln_account_exclusion__v	data_change_request__v
aln_account_territory__v	account_territory__v
aln_roster_member__v	user__sys

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.

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.

Deactivating Assignments of Deleted Records

Accounts, addresses, and Parent HCOs deleted from Vault CRM since the last import are deactivated in Align and have their crm_is_deleted__v field automatically set to Yes. This means it is possible for a new Vault CRM record to have the same External ID as a previously deleted record. When these new records with duplicate External IDs import into Align, they may initially be marked as errors due to an ID conflict. A later stage in the import process automatically reconciles the IDs.

Account merges are not currently supported.

If an address or Parent HCO is deleted from Vault CRM, the respective status__v fields are set to inactive__v. Geography or hierarchy-based assignments are no longer generated for those records on subsequent rule runs. Assignments based on them will not be end-dated until the first rules run after the import.

If a Vault CRM user is deactivated, the status__v field on the corresponding aln_roster_member__v record is set to inactive__v. All manual assignments for this roster member are end-dated.

When territory__v or user_territory__v records are deleted in Vault CRM, the corresponding aln_territory__v and aln_roster_member_territory__v records remain active. Integration Status records are created for each of these records to indicate the deletion in Vault CRM. This enables admins to review the changes and choose to either deactivate the records in Align or keep them active.

The process also imports new account_territory__v records from Vault CRM. Align creates matching aln_account_territory__v records, but only if both the associated account and territory already exist in Align. Unmatched records are logged with an error. New assignments inherit the end date of their corresponding territory in Align.

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.

Vault CRM assignments resulting from multiple overlapping Align assignments are not deleted until the last Align assignment expires. Once the Vault CRM record is deleted, the engine will create as many rows in the log files as there were Align assignments associated with it.

Admins can initiate pushes to Vault CRM at either the root level or at the territory level.

Pushing at the Root Level

Pushing at the root level 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.