Page Comparison

...

• MDM provides uniqueness rules to prevent data record duplication prevention in the case where a simple displayProperty won't suffice.
• Optionally, specify a comma-separated list of domain properties whose values, in aggregate, must be unique across all the data records for the domain.
• If not provided, MDM will use the displayProperty as the uniquenessRules.
• Uniqueness rule properties are limited to type STRING
• Values in uniquenessRules properties are case sensitive e.g. "California" is NOT equal to "california"

...

Federated Domains, Uniqueness Rules and Required Properties

The goal for federated domains is to keep the combined list of:

1. Properties in the uniqueness rules to a minimum
2. Properties defined with the "required" option (see "required" option for properties)  to a minimum

If the list is long, some adaptors that are associated with the domain might not contain all of the properties and will be unable to add new records to a data domain.

It is important that for an service associated with a domain that should have the scope to create data records for a domain, that it stores or has access to all of the properties that are defined with the "required" optoin and that are part of the uniqueness rules list.

Valid Property Names

• Must start with a letter or "\_" (underscore).
• Can contain digits, "-" (dash) and "\_" (underscore) only.
• Can be up to 64 characters in length.
• Are case in-sensitive.
• If two properties have the same name at the same level only one will be used. In Example 1 below, only one name "property" will be used. In Example 2, both will be used  because "name" occurs at different levels in the JSON structure.

...