Handling Account Merges in Align

Account merges are reflected in Vault CRM through regular imports. Record conflicts can occur during an import when values from external ID fields from a losing account__v are copied into winning accounts. The conflict arises from the same external ID being used across two account__v records for which Align is not supported.

Who can use this feature?

  • Browser Users
  • Users require an Align License
  • Align Operational Users

Configuring Handling Account Merges in Align for

To configure this feature, ensure the following features are configured:

Handling Account Merges in Align as

To avoid record conflicts in Align after a Vault CRM import, the External IDs of losing accounts are edited in Align during Vault CRM account merges. Align completes the following steps when processing account merges during a Vault CRM import:

  1. Align queries Vault CRM for accounts with an in_merge__sys field of duplicate__sys.

  2. Align imports the losing account__v records and processes them in the following way:

    • The status__v field on the account__v object is set to inactive__v

    • All unique fields on the account__v have their value appended with ::MergedWith::<ID of the Winning Account>

      For example, the losing account’s external_id__v field on the account__v object is set to 12345. The winning account has a value of 6789. After the merge, the losing account in Align has an external_id__v field of 12345::MergedWith::6789.

      Align only supports unique fields of type Text and not of type Number.

    • All open Territory assignments are end dated for the losing account
  3. Remaining accounts import.

Account Merges in MCCP Targeting

If accounts are merged in Vault CRM that are associated with MCCP targets, the following update also occurs in Align as part of the account merge process:

Merged

Vault CRM Accounts

Merge Import Behavior into the Current Production Cycle in Align

Merge Import Behavior into the Upcoming Modeling Cycle in Align

The winning account is a target

The mc_cycle_plan_target__v record is not updated, since the losing account is not a target.

The losing account is a target

The target__v field of the mc_cycle_plan_target__v records for both the production and modeling cycles update to instead reference the winning account. The records remain active.

An entry noting the successful merge is added to the SUCCESSFILES_IMPORTFROMCRM folder of the import process.

Both the winning and losing accounts are targets

  • The mc_cycle_plan_target__v record associated with the winning account is not changed.

    The following fields are updated on the mc_cycle_plan_target__v record associated with the losing account:

    The status__v field updates to inactive__v
  • The target__v field updates to instead reference the winning account

  • The external_id__v and targeting_id__v fields are appended with the following:

    ::MergedWith::<CRM.Target.Id of the Winning Account>

An entry noting the successful merge is added to the SUCCESSFILES_IMPORTFROMCRM folder of the import process.

The mc_cycle_plan_target__v record associated with the winning account is not changed.

The mc_cycle_plan_target__v record associated with the losing account is deleted. Any mc_cycle_plan_channel__v and mc_cycle_plan_product__v records associated with the target are also deleted.

An entry noting the successful merge is added to the SUCCESSFILES_IMPORTFROMCRM folder of the import process.

Related Topics

Merging Duplicate Account Records

Using Account Assignment Rules in Align

Manually Managing Account Assignments in Align