Updating records by record state
DM
Use an advanced property to determine which records should be updated based on record state.
Updates to non-valid records (merge losers, invalid, or deleted records) typically have no benefit because they are not visible in the Network UI. Updates to merge losers after they have been merged are not shared with the winning record. So, although these updates are lost, they are still processed in other subscription jobs (for example, target subscriptions). You can use this property to specify that only Valid records are updated to reduce processing times.
If the property is not defined, the default behavior (ANY) is applied to new and existing subscriptions to ensure that existing behavior in your source subscription does not change.
Advanced property
Add the property to the Advanced Mode in your source subscription to determine the records that are updated.
Property
job.merge.allowUpdatesForRecordsWithState
Supported values
- ANY (default)
- VALID
- INVALID
- UNDER_REVIEW
- MERGED_INTO
The property supports the non-valid record options because there might be situations where you need to make updates to non-valid records.
This property only applies when updates are done through key matching (using custom keys and/or Network Entity IDs (VIDs)) within a source subscription. Updates to non-valid records should be uncommon because custom keys are typically copied to the surviving record in a merge or inactivated in other situations, so key matching directs the incoming update to the valid record.
Job details
If a source subscription attempts to update a record whose record state is different from the property value in that subscription, a warning displays in the Job Error section. You can investigate the incoming updates further; for example, if updates were attempted to a merge loser, you might want to add them to the merge winner.