Configuration is not needed for this feature.

Records are processed in Vault CRM based on their record_state__v in Network. If the record is new to Vault CRM and the record state is not VALID or UNDER_REVIEW, the record is not imported.

The following tables define what is imported to Vault CRM based on the record state in Network:

Entity	Record State	Action	Note
Account	VALID	Sync to Vault CRM via import or subscription
	DELETED INVALID	If the record is new to Vault CRM, it is not imported. If the record exists in Vault CRM: • Territories assigned using ATL are removed from the account. The territories removed using ATL are determined by the ATL Mode. See Processing Changes to ATL Records for details. • Customer Master Status = Rejected
	MERGED_INTO	If record exists in Vault CRM, it is merged. If it is new, it is not imported.
	MERGE_INACTIVATED MERGE_ADDED	These record state values only apply to child entity
	UNDER_REVIEW	The record is imported to Vault CRM, Account Customer Master Status is set to Under Review	Only if Data Change Request Mode Veeva Setting is set to 2

 

Entity	Record State	Action	Note
Child Account	VALID	Sync to Vault CRM via import or subscription
	DELETED MERGED_INTO MERGE_INACTIVATED MERGE_ADDED INVALID	The record is deleted in Vault CRM
	UNDER_REVIEW	The record is not imported to Vault CRM

 

Entity	Record State	Action	Note
Address	VALID	Sync to Vault CRM via import or subscription
	DELETED MERGE_INACTIVATED INVALID	If the record is new to Vault CRM, it is not imported. If the record exists in Vault CRM, the Inactive flag is selected and the customer_master_status__v field on the Address object is set to rejected__v.
	MERGED_INTO MERGE_ADDED	If the selected address exists in Vault CRM, the Inactive flag is selected on the merge loser address and the customer_master_status__v field on the Address object is set to rejected__v. All field values that do not exist in the merge winner address are copied to the winner address. If a merge winner does not exist in Vault CRM when a merge is propagated, instead of setting the loser address to inactive and the customer_master_status__v field to rejected__v, the loser address is updated with the winning address' Network external Id.
	UNDER_REVIEW	The record is imported to Vault CRM, Address Customer Master Status is set to Under Review	Only if Data Change Request Mode Veeva Setting is set to 2

Vault CRM uses a flag (inactive__v) on Address object to indicate address status, while Network uses picklist address_status__v. In order to ensure address status is consistent, it is recommended to create a field in Vault CRM with the same picklist values, and map it to address_status__v. To populate the inactive__v field in Vault CRM, you can create a custom boolean field in Network on the Address object with a NEX rule. For example:

IF( address_status__v == 'I' || (record_state__v IN ['INVALID','DELETED','MERGE_INACTIVATED']),'Y', 'N')

The Required / Update and Calculate for search results from OpenData settings should be enabled.

An alternative is to create a Transformation Rule in Network.

Map that custom field in Network to the inactive__v field in Vault CRM.

Entity	Record State	Action	Note
License	VALID	Sync to Vault CRM via import or subscription
	DELETED MERGED_INTO MERGE_INACTIVATED MERGE_ADDED INVALID	Remove all relevant license values on the associated address
	UNDER_REVIEW	The record is not imported to Vault CRM

A MERGE_INACTIVATED record state occurs in two cases: when a customer-owned record is merged with a Vault-owned record or when two Vault-owned records are merged in the Master system. In the first scenario, the Vault-owned record takes priority and the children of the customer-owned record are deactivated. In the second scenario, the children of the losing record are deactivated.