_upstream=true
indicator so the dCDR service sends the original request to the central server directly. This means that these functions should only be called when online and connected to the iCDREntityRelationship
resources in the CDR. However this method is discouraged as EntityRelationship
properties require specific attributes/values in order for MDM to function correctly.LOCAL
record (in which case results are the corresponding MASTER
records) or the UUID can represent a MASTER
record (in which case the results are the corresponding LOCAL
records). Operations on global resources are match pairs since there is no context.Match
and autoLink
is turned off, orMatch
regardless of autoLink
, orProbable
EntityRelationship
pairs which represent the candidate local holder
and the candidate master target
.MASTER
records to which the current local is a candidate or LOCAL
records for which current master has candidates).$match.score
tag on the returned object is the original score that candidate had with the focal record.DELETE
against the candidate record and instructs the matcher to never consider the record as a candidate again (establishes an IGNORE record). EntityRelationship?relationshipType.mnemonic=MDM-Master
with the exception that the caller does not need to know whether the identifier passed as the parameter is a master or a local record.DELETE
the mdm-link
between two objects. This call does not rely on the order of parameters so long as the scoping key and the child key represent a MASTER/LOCAL pair. For example, this call:mdm-link
resource ensures that only a LOCAL record is linked with a MASTER record. This differs from a MERGE operation where LOCAL>LOCAL and MASTER>MASTER merges can be performed (and it called via the $merge
operation since $merge
does not rely on MDM logic). $merge
operation, however the source and target UUIDs must be a local and master respectively.POST
an Reference
with the id
carrying the UUID of the master to which the attaching is to occur (or if the focus UUID on the URL is a MASTER then the UUID of the local).id
in the Entity
are ignored.mdm-configuration
resource on the AMI. The configuration APIs allow callers to enable, or disable