Working with source inactivation detection
DM
When a source no longer uses and manages a record, Network should also disassociate the custom keys for that source from the record. By doing this, Network knows that the entity won't be managed from that source any longer and won't expect updates for the record using the source's custom key.
Some sources indicate that a record is no longer managed by omitting it from the data feed. When source inactivation detection is enabled for a subscription, the data load detects the records that are missing from the source feed. The custom keys for the missing records are marked as Source Deactivated in Network.
Sub-objects
When custom keys for an HCP or HCO are source deactivated (SD), the active status of sub-objects (Address, License, and Parent HCO) does not change. However, if a sub-object is omitted from the source feed, the custom key for the sub-object is source deactivated, even when the entity (HCP or HCO) remains active.
Source inactivation detection and merge
When source inactivation detection is enabled and records are merged, the losing key is migrated to the winning record and the losing custom key is set to Source Deactivated in the winning record.
View custom key status
To see the status of a custom key, view a record profile and expand the External Identifiers section.
Example of the process
Review the following example to see how the custom keys for an omitted record in a feed are source deactivated in Network and then reactivated.
January
An initial file is loaded to Network from a SAP® subscription. Source inactivation detection is enabled for the subscription.
| Source ID | First Name | Last Name | City | State |
|---|---|---|---|---|
| 433 | John | Smith | Chicago | IL |
| 568 | Bob | Woods | New York | NY |
| 369 | Mary | Turner | Miami | FL |
Result: Custom keys are added to the records in the Network instance for this subscription.
For example, Network adds custom keys for the SAP subscription to the existing HCP record for Bob Woods:
| VID Key (Custom Key) | Status | Status Update |
|---|---|---|
| SAP:HCP:568 | Active | 01-01-2016:00:12:26 |
| SAP:ADDRESS:568 | Active | 01-01-2016:00:12:26 |
| AXIS:AXIS:213 | Active | 12-01-2015:03:30:15 |
February
A second file is loaded for the SAP subscription. Source inactivation detection is enabled for the subscription. The HCP record for Bob Woods is missing from the SAP feed.
| Source ID | First Name | Last Name | City | State |
|---|---|---|---|---|
| 433 | John | Smith | Chicago | IL |
| 369 | Mary | Turner | Miami | FL |
Result: The custom keys for Bob Woods for the SAP subscription are set to Source Deactivated in the Network instance.
| VID Key (Custom Key) | Status | Status Update |
|---|---|---|
| SAP:HCP:568 | Source deactivated | 02-01-2016:00:12:26 |
| SAP:ADDRESS:568 | Source deactivated | 02-01-2016:00:12:26 |
| AXIS:AXIS:213 | Active | 01-01-2016:03:30:15 |
March
A third file is loaded. Source inactivation detection is enabled for the SAP subscription. The HCP record for Bob Woods is included in the feed again.
| Source ID | First Name | Last Name | City | State |
|---|---|---|---|---|
| 433 | John | Smith | Chicago | IL |
| 568 | Bob | Woods | New York | NY |
| 369 | Mary | Turner | Miami | FL |
Result: Custom keys for Bob Woods for the SAP subscription are activated again in the Network instance.
| VID Key (Custom Key) | Status | Status Update |
|---|---|---|
| SAP:HCP:568 | Active | 03-01-2016:00:12:26 |
| SAP:ADDRESS:568 | Active | 03-01-2016:00:12:26 |
| AXIS:AXIS:213 | Active | 02-01-2016:03:30:15 |
Merging records with source deactivated custom keys
Active custom keys are retained when a record is merged with a record that has an identical custom key that is source deactivated. The active custom key from the losing record is copied over to the winning record to ensure that the winning record has an active key.
Example
This merge behavior occurs when locally managed records are merged and when Veeva OpenData records are merged.