Publisher is Ignored in a Consolidation

Owned by Former user (Deleted)
Last updated: Mar 27, 2018 by Matthew Dahlman (Deactivated)
1 min read

Problem

When loading data into the hub, a given publisher seems to be ignored in record-level or field-level consolidation in Convergence for MDM.
This publisher is used either in a Preferred Publisher or in Custom Ranking consolidation strategy.

Solution

The value stored and expected by Convergence for MDM to identify the publisher of a record is the Publisher Code, and not its Name. Best practice:

  • Codes in UPPERCASE
  • Names in MixedCase

There are several reasons for a preferred publisher to be ignored in a consolidation:

  • The Data loaded in the SD_ table do not use the Publisher Code in the B_PUBID column. This publisher code is case-sensitive. The data integration job must use the case-sensitive Publisher Code. In most circumstances this should be ALL CAPS.
    If the value in B_PUBID does not match an existing publisher code, then this publisher is considered at the last position in the preferred publisher consolidation. Other publishers' values will always be taken into account for consolidation.
  • When the PublisherID built-in attribute is used in a Custom Ranking consolidation, the literal values specified in the SemQL expression should be equal to the Publisher Code. These values are also case sensitive.
    If the SemQL clause does not contain a literal that exactly matches the publisher codes, the clause will not work as expected.