L3 Validation Errors

The following table lists the L3 errors, including error code, error message, detailed error message, under what circumstances the error can occur, and how to resolve the problem.

Table 1. L3 Validation Errors
Internal Parameter Name Error Details Error Analysis Error Resolution
ATTRIBUTE_MODEL_NOT_FOUND Error Code 170

Error Message Reference or nested attribute with name name not defined in entity type type name.

Detailed Error Message Failed to parse entity of the specified type; it has a complex attribute not defined in the model.
Some piece of the configuration (a match rule, a match field in a nested attribute, and so on.) refers to an attribute that doesn't exist in the entity type. Fix the attribute name to a correct one.
INVALID_NESTED_ATTRIBUTE_CONFIGURATION Error Code 219

Error Message Invalid matchOvOnly section for nested attribute with attributeURI URI.

Detailed Error Message For a tenant that has flatOvCalculation property = true it is forbidden to use matchOvOnly for nested attributes.
One of the nested attributes from the request violates the restriction about mixing flat Operational Value (OV) calculation with the matchOvOnly field for nested attributes. Set the matchOvOnly field to false or change a value of the flatOvCalculation field in the L3 if it's incorrect.
INCOMPLETE_ATTRIBUTE_ORDERING_SECTION Error Code 220

Error Message Incomplete attributeOrdering section for attribute with attributeURI URI.

Detailed Error Message FieldBasedOrderingStrategy requires fieldURI field.
A fieldURI field from an attributeOrdering section is not set or it is empty. Set a correct value in the fieldURI field.
INVALID_ATTRIBUTE_ORDERING_SECTION Error Code 221

Error Message Invalid attributeOrdering section for attribute with attributeURI URI. Attribute with attributeURI URI, defined in attributeOrdering section is not simple or is absent.

Detailed Error Message
FieldBasedOrderingStrategy
requires fieldURI field which can refer only to simple attributes.
An attribute on which attributeOrdering section refers is not simple or does not exist. Refer a correct value in the attributeOrdering section.
INVALID_ATTRIBUTE_ORDERING_SECTION_SIMPLE_ATTR Error Code 222

Error Message Invalid attributeOrdering section for attribute with attributeURI URI.

Detailed Error Message Field-based attribute ordering strategy is applicable only for complex attributeValues types like nested or referenced.
An attributeOrdering section is described for a simple attribute for which ones are not applicable for ordering. Remove the attributeOrdering section from the simple attribute.
INVALID_ATTRIBUTE_AUTO_GENERATED_SECTION Error Code 233

Error Message Invalid auto-generation settings for attribute uri.

Detailed Error Message If autoGenerated=true is specified then generator and autoGenerationPattern for simple and autoGenerationNestedPattern for nested attributes must be specified. Only String attributes or sub-attributes can be auto-generated. Auto-generation could not be specified for reference attributes.
Auto-generated attributes have the set of rules which are described at the detailed message of this error. The request violates at least one of them. Find what a type of requirement from the detailed message was violated in the request and fix an error.
INVALID_ATTRIBUTE_AUTO_GENERATED_PATTERN Error Code 234

Error Message Invalid auto-generation pattern for attribute URI.

Detailed Error Message The auto-generation pattern must have the proper number of open and close braces. Braces must be specified properly.
An autoGenerationPattern (or a pattern from autoGenerationNestedPattern for nested attributes) has an incorrect format. Fix the format of the pattern field.
INVALID_SOURCE_AUTO_GENERATED_SECTION Error Code 235

Error Message Invalid auto-generation settings for source type uri.

Detailed Error Message If autoGenerated=true is specified then generator and autoGenerationPattern must be specified.
A source type in the configuration is marked as autoGenerated but doesn't have a definition of a generator name or an autogeneration pattern. Add generator or autoGenerationPattern field if one or both of them are not specified for the source type, or mark the source as not autoGenerated.
INVALID_SOURCE_AUTO_GENERATED_PATTERN Error Code 236

Error Message Invalid auto-generation pattern for source type uri

Detailed Error Message The auto-generation pattern must have the proper number of open and close braces. Braces must be specified properly.
An autoGenerationPattern has an incorrect format. Fix the format of the pattern field.
APPLYING_GENERATOR_TO_REFERENCE_ATTRIBUTE_ERROR Error Code 240

Error Message Generator shouldn't be applied to the reference attribute uri.

Detailed Error Message Generator must be applied to either attributes of referenced entity or to attributes of relation.
It is forbidden to use generator for referenced sub-attributes directly. Remove the autoGenerated section or move those parameters to an attribute configuration of the referenced entity type or the referenced relation.
IMPROPER_SUBATTRIBUTE_AUTO_GENERATED_SECTION Error Code 243

Error Message Improper auto-generation section for sub-attribute uri.

Detailed Error Message Sub-attribute uri cannot be auto-generated because it's already specified at the autoGenerationNestedPattern section of its parent attribute uri.
For a nested sub-attribute there are two ways to set an autogeneration pattern: via autoGenerationNestedPattern of the nested attribute or directly via autoGenerationPattern of the attribute itself. You must use only one of them; that is, don't mix. Choose only one way to set an autogenerated pattern for the simple sub-attribute, and remove the other one.
ERRORS_IN_BUSINESS_CONFIGURATION Error Code 270

Error Message One or few errors was found during validation of the Reltio Business Model.

Detailed Error Message Validation of the Reltio Business Model failed. See foundErrors in the section below.
General errors that shows that the configuration posting failed. See foundErrors for details.
ATTRIBUTE_URIS_NOT_FOUND_IN_MATCH_URIS Error Code 277

Error Message Some keyAttributeURIs not found in the matchFieldURIs.

Detailed Error Message Validation of Nested attribute failed. keyAttributeURIs must be a subset of matchFieldURIs, or keyAttributeURIsExactOrNull must be subset of matchFieldURIsExactOrNull, or keyAttributeURIsExactOrAllNull must be subset of matchFieldURIsExactOrAllNull.

When you define the keyAttributeURIs, but you did not define the matchFieldURIs.

You did not define one or more keyAttributeURIs in the matchFieldURIs set.

You defined keyAttributeURIsExactOrNull, but you did not define matchFieldURIsExactOrNull.

You did not define one or more keyAttributeURIsExactOrNull in the matchFieldURIsExactOrNull set.

You defined the keyAttributeURIsExactOrAllNull, but you did not define matchFieldURIsExactOrAllNull.

You did not define one or more keyAttributeURIsExactOrAllNull in the matchFieldURIsExactOrAllNull set.

Edit the configuration to correct the discrepancy.

Define the keyAttributeURIs in the matchFieldURIs

Define keyAttributeURIsExactOrNull in matchFieldURIsExactOrAllNull.

Define keyAttributeURIsExactOrAllNull in matchFieldURIsExactOrAllNull

KEY_OR_MATCH_ATTRIBUTE_URIS_NOT_FOUND Error Code 278

Error Message Attributes {0} defined in keyAttributeURIs/matchFieldURIs are not found in the nested attribute {1}.

Detailed Error Message Attributes defined in keyAttributeURIs/matchFieldURIs are not found in the nested attribute.
Attribute present in the keyAttributeURIs/matchFieldURIs section of a nested attribute is not defined in that nested attribute. Check and correct the attribute definition or remove the invalid attribute.
INVALID_ATTRIBUTE_CONFIGURATION Error Code 281

Error Message The attribute {0} has type {1}, and this type does not support part of defined parameters.

Detailed Error Message The attribute {0} has type {1}, and this type does not support parameters like {2}.
For example, you have a nested attribute type and this type does not support parameters, such as referencedAttributeURIs, relationshipTypeUri, referencedEntityTypeUri, and relationshipLabelPattern. Check attribute type definition and remove the extra parameters from its configuration.
METADATA_SCHEMA_INVALID Error Code 303

Error Message Reltio Business Model schema specification cannot be parsed as XSD.

Detailed Error Message The Reltio Business Model schema stored in the Metadata column family in the database has errors.
The system verification schema that is stored in the database is corrupted. Please contact Support and report this error.
METADATA_SCHEMA_VALIDATION_FAILED Error Code 304

Error Message Failed to validate the business model. Validator failed on element value with error: details.

Detailed Error Message The validation of the Reltio Business Model the user is trying to create has failed. For details about the validation error see the short error message. Validation is being performed by the XSD specification of RBM,
The request has an incorrect JSON format (an unknown field, forbidden duplicates, and so on.). See message details and fix the error found in the JSON request.
METADATA_URI_NOT_FOUND Error Code 312

Error Message URI not found in uri.

Detailed Error Message The URI specified in the request is not found in the configuration. Please pay attention that the URI must contain the full path like configuration/entityTypes/Type instead of just Type.
A uri that is used as a property of the survivorship mapping (comparisonAttributeUri; filterAttributeUri; primaryAttributeUri) refers to a non-existent attribute. Fix the value of the faulty field; set an attribute that exists.
METADATA_RESOURCE_NOT_FOUND Error Code 313

Error Message Resource not found uri.

Detailed Error Message Resource specified in the request is not found.
A resource that is referred by some uri does not exist in the business model. Add a resource with the specified uri, or fix the uri if you made a mistake in it.
METADATA_MODEL_PATH_ELEMENT_NOT_FOUND Error Code 314

Error Message Model category not found uri.

Detailed Error Message Model category specified in the request was not found.
A uri that is specified in the request is incorrect. Fix the value of an incorrect uri.
METADATA_MODEL_URI_SHOULD_START_WITH_CONFIG Error Code 315

Error Message Model URI uri must start with configuration resource.

Detailed Error Message Model URI specified does not belong to configuration resources.
A uri that is specified in the request does not start with a configuration/ prefix. Add a configuration/ prefix to the faulty uri, and check that it is correct.
METADATA_DEPENDENT_LOOKUP_ATTRIBUTE_HAVE_CIRCULAR_DEPENDENCY Error Code 333

Error Message Circular dependency found between attribute uri {0} and {1} for EntityType {2} in dependentLookupAttributes configuration.

Detailed Error Message It is not allowed to define circular dependencies for dependentLookupAttributes. Circular dependency found between attribute uri {0} and {1} for EntityType {2} in dependentLookupAttributes configuration.
For an entity, if attribute A has dependentLookupAttributes as B and attribute B has dependentLookupAttributes as A, a circular dependency is created. Remove one of the dependentLookupAttributes to ensure that there is no circular dependancy.
METADATA_DEFAULT_AS_SURROGATE_CROSSWALK Error Code 334

Error Message Default crosswalk is configured as a surrogate crosswalk.

Detailed Error Message It is not allowed to specify a default crosswalk Source System in the surrogateCrosswalks section.
It is forbidden to use a default source system as a surrogate crosswalk for an entity type. Change a source type for the surrogate crosswalk section, or remove the entire surrogate section. Make sure that the default source is correct (the defaultCrosswalk field in the tenant physical configuration); change it if required.
METADATA_MISSED_COMPARISON_ATTRIBUTE_URI Error Code 335

Error Message Survivorship group mapping of attribute uri {0} to strategy {2} is incorrect in {1}.

Detailed Error Message comparisonAttributeUri property is required for a complex attribute if MinValue or MaxValue strategy is used.
A Min/MaxValue survivorship strategy can compare only simple (scalar) values, so for nested/referenced attributes a one sub-attribute must be chosen for comparison. The passed configuration doesn't have the comparisonAttributeUri field which describes that attribute. Specify an attribute that must be used for comparison of nested/referenced attributes in the comparisonAttributeUri field for the survivorship group mapping.
METADATA_COMPARISON_ATTRIBUTE_IS_NOT_SUBATTRIBUTE Error Code 336

Error Message Survivorship group mapping is incorrect for attribute name in uri.

Detailed Error Message comparisonAttributeUri=value in uri is not a sub-attribute of the attribute name.
A Min/MaxValue survivorship strategy can compare only simple (scalar) values, so for nested/referenced attributes a one sub-attribute must be chosen for comparison. The passed comparisonAttributeUri, which describes that attribute, is not a sub-attributed of the compared attribute. For comparison of the nested/referenced attribute, choose a sub-attribute of it, and use that attribute in the comparisonAttributeUri field.
METADATA_COMPARISON_ATTRIBUTE_IS_NOT_SIMPLE Error Code 337

Error Message Survivorship group mapping is incorrect for attribute name in uri.

Detailed Error Message comparisonAttributeUri=value, which used in mapping uri for the attribute name, is not a simple attribute.
A Min/MaxValue survivorship strategy can compare only simple (scalar) values, so for nested/referenced attributes a one sub-attribute must be chosen for comparison. The passed comparisonAttributeUri, which describes that attribute, is not simple. For comparison of the nested/referenced attribute, choose a sub-attribute that is simple, and use it in the comparisonAttributeUri field.
METADATA_FILTER_ATTRIBUTE_IS_NOT_SIMPLE Error Code 338

Error Message Survivorship group mapping is incorrect for attributename in uri.

Detailed Error Message The attribute, which is used for equals criteria in filter (value) in mapping uri for the attribute name, is not a simple attribute.
For filtering values in the survivorship group you must use only simple attributes. Choose a simple attribute for filtering in the survivorship group
METADATA_SURVIVORSHIP_GROUP_MAPPINGS_DUPLICATED Error Code 339

Error Message Survivorship group (uri) configuration is incorrect.

Detailed Error Message There are duplicates in mapping for survivorship group with uri uri.
A survivorship group contains some duplicated mappings. That can occur if a user described mappings for the same attribute (and, optionally, with the same filter) multiple times. Check all mappings inside the survivorship group for duplicates, and leave only one of them (a correct one).
METADATA_DEPENDENT_ATTRIBUTES_CONTROL_ATTRIBUTE_DUPLICATED Error Code 340

Error Message Duplicated control attribute URI: uri.

Detailed Error Message The dependent attributes configuration contains several entries with the same control attribute URI.
Some attribute is defined twice as a control attribute in the dependentAttributes section. Find the duplicate values in the attributeUri field at the dependAttributes section, and leave only one of them.
METADATA_DEPENDENT_ATTRIBUTES_ATTRIBUTE_DUPLICATED Error Code 341

Error Message Duplicated attribute URI: uri.

Detailed Error Message The dependent attributes configuration contains several entries with the same dependent attribute URI.
All attribute names that are mentioned in a dependentAttributes section must be unique and must not be used more than once Find duplicates that are mentioned multiple times as an attribute name in the dependentAttributes section, leave only one of them, and remove other ones. Duplicates can be mentioned in vertical configurations.
METADATA_ATTRIBUTE_NOT_DEFINED Error Code 342

Error Message Attribute with URI uri not defined in entity type uri.

Detailed Error Message The attribute with the specified URI is not defined for the entity type.
An attribute that is mentioned in a dependentAttributes section does not exist. Fix the non-existent attribute name, or introduce a new attribute with this name for the entity type.
METADATA_NO_LOOKUP_CODE_FOR_ATTRIBUTE_WITH_DEPENDENT_LOOKUPS Error Code 347

Error Message Dependent lookups configuration error: uri.

Detailed Error Message It is not allowed to have dependent lookups for attribute without lookup code uri.
An attribute that is mentioned in a dependentAttributes section does not exist. Add a lookupCode field to the simple attribute.
METADATA_DEPENDENT_LOOKUP_ATTRIBUTE_NOT_FOUND Error Code 348

Error Message Dependent lookups configuration error: uri.

Detailed Error Message Configured dependent lookup attribute name is missing in type uri.
An attribute that is mentioned in a dependentLookupAttributes section doesn't exist. Fix the attribute name to a correct one or remove it.
METADATA_DEPENDENT_LOOKUP_ATTRIBUTE_IS_NOT_SIMPLE Error Code 349

Error Message Dependent lookups configuration error: uri.

Detailed Error Message Configured dependent lookup attribute is not a simple attribute name in type uri.
An attribute that is mentioned in a dependentLookupAttributes section is not simple; only simple attributes are allowed for this section. Fix the attribute to a simple one or remove it.
MATCH_SERVICE_CLASS_NOT_FOUND Error Code 350

Error Message Match service class not found name.

Detailed Error Message The match service class is not found.
The match service class mentioned in matchServiceClass doesn't exist. Fix the match service class name or remove it. By default, com.reltio.businesslogic.match.providers.internal.InternalMatchService will be used.
MATCH_TOKEN_CLASS_NOT_FOUND Error Code 351

Error Message Match token class not found name.

Detailed Error Message The match token class is not found.
The match token class defined in a matchTokenClass or matchTokenClasses mappings doesn't exist. Fix the match token class name or remove it. For the attributes mentioned in an exact section and in a fuzzy section, by default, com.reltio.match.token.ExactMatchToken will be used. For the attributes mentioned in a multi operand, by default, com.reltio.match.token.ExactMultiToken will be used.
MATCH_COMPARATOR_CLASS_NOT_FOUND Error Code 352

Error Message Match comparator class not found name.

Detailed Error Message The match comparator class is not found.
Match comparator class defined in a comparatorClass or comparatorClasses mappings doesn't exist. Fix the comparator class name or remove it. For the attributes mentioned in an exact section and in a fuzzy section, by default, com.reltio.match.comparator.BasicStringComparator will be used. For the attributes mentioned in a multi operand,by default, com.reltio.match.comparator.ExactMultiComparator will be used.
METADATA_MATCH_RULE_INVALID_SPECIFICATION Error Code 353

Error Message Match rule specification error: value.

Detailed Error Message The process failed because of an invalid match rule specification in the Reltio Business Model.
An attribute defined in comparatorClasses or matchTokenClasses mappings is not simple, or an attribute defined in these mappings is not applicable for matchTokenClass or comparatorClass by its type. Use a simple attribute in comparatorClasses or matchTokenClasses mappings, and choose comparatorClass and matchTokenClass according to its type.
METADATA_NEGATIVE_MATCH_RULE_INVALID_SPECIFICATION Error Code 354

Error Message Negative match rule specification error: value.

Detailed Error Message A negative match rule specification error in the configuration.
An attribute defined in comparatorClasses of a negative match rule mappings is not simple, or an attribute defined in this mapping is not applicable for comparatorClass by its type. Use a simple attribute in comparatorClasses mapping and, choose comparatorClass according to its type.
WRONG_MATCH_CLASS_PARAMETER Error Code 355

Error Message Provided parameter is not supported by match class.

Detailed Error Message Class name (from rule " <rule> ") does not support parameter with the following mapping: <mapping>.
Wrong name or type of the parameter defined for comparatorClass or matchTokenClass. Use names and types of the parameters for comparatorClasses and matchTokenClasses according the documentation.
ATTRIBUTE_TYPE_IS_NOT_SUPPORTED_IN_MATCHING Error Code 356

Error Message Attribute type is not supported by match class.

Detailed Error Message Match class <class> does not accept attributes of type type.
An attribute defined in comparatorClasses or matchTokenClasses mappings is not applicable for comparatorClass or matchTokenClass by its type. Choose comparatorClass and matchTokenClass according to the attribute's type.
MATCH_TOKEN_CLASS_INVALID Error Code 357

Error Message Invalid match token class name.

Detailed Error Message Match token class must belong to a special hierarchy.
Match token class defined in a matchTokenClass or matchTokenClasses mappings doesn't implement the MatchToken interface. Match token class must implement the MatchToken interface.
MATCH_COMPARATOR_CLASS_INVALID Error Code 358

Error Message Invalid match comparator class name.

Detailed Error Message Match comparator class must belong to a special hierarchy.
Comparator class defined in comparatorClass or comparatorClasses mappings doesn't implement the Comparator interface. Comparator class must implement the Comparator interface.
MATCH_SERVICE_CLASS_INVALID Error Code 359

Error Message Invalid match service class name.

Detailed Error Message Match service class must belong to a special hierarchy.
Match service class mentioned in matchServiceClass doesn't implement the IMatchService interface. Match service class must implement the IMatchService interface.
MATCH_DOCUMENT_COMPARATOR_CLASS_NOT_FOUND Error Code 360

Error Message Document comparator class not found name.

Detailed Error Message Document comparator class not found.
Document comparator class mentioned in documentComparator section doesn't exist. Fix the document comparator class name.
MATCH_DOCUMENT_COMPARATOR_CLASS_INVALID Error Code 361

Error Message Invalid document comparator class name.

Detailed Error Message Document comparator must belong to a special hierarchy.
Document comparator class mentioned in documentComparator section is not assignable from DocumentComparator class. Document comparator class mentioned in documentComparator section must be assignable from DocumentComparator class.
METADATA_CONFIGURATION_VERIFICATION_STATUS_INVALID Error Code 364

Error Message Invalid verification status value.

Detailed Error Message Verification status must belong to (Verified, Partially Verified, Unverified, Ambiguous, Conflict, or Reverted) list.
In the Loqate cleanse function you're trying to use an unknown verification status. For the verification status use one value from the allowed list (see more in Using AVC to set Address Verified StatusUsing AVC Code to set Address Verified Status).
METADATA_CONFIGURATION_VERIFICATION_STATUS_REGEXP_INVALID Error Code 365

Error Message Invalid verification status regular expression: value.

Detailed Error Message Invalid verification status regular expression: value.
A regular expression you're trying to put has an incorrect format. Fix the format of the regular expression to a correct one (see more in Using AVC to set Address Verified StatusUsing AVC Code to set Address Verified Status).
METADATA_USE_SOURCES_FOR_OV_IS_EMPTY Error Code 366

Error Message Parameter sourcesForOv is empty in survivorship group uri.

Detailed Error Message Parameter sourcesForOv is empty. Please specify sources or remove this parameter.
A mapping contains sourcesForOv field which is empty. Find an empty sourcesForOv field in the survivorship group mapping. Add at least a one source to this field or remove it.
MATCH_RULE_CLEANSE_ADAPTER_CLASS_NOT_FOUND Error Code 368

Error Message Match rule cleanse adapter class not found name.

Detailed Error Message The match rule cleanse adapter class not found.
The cleanseAdapter class defined in the match rule's cleanse section doesn't exist. Fix the cleanse adapter class name or remove it.
MATCH_RULE_CLEANSE_ADAPTER_CLASS_INVALID Error Code 369

Error Message Invalid match rule cleanse adapter class name.

Detailed Error Message The match rule cleanse adapter class must belong to a special hierarchy.
The cleanseAdapter class defined in the match rule's cleanse section doesn't implement the CleanseEngine interface. The cleanseAdapter class defined in the match rule's cleanse section must implement the CleanseEngine interface.
METADATA_CONFIGURATION_LOQATE_OPTIONS_INVALID Error Code 370

Error Message Invalid Loqate options value.

Detailed Error Message Loqate options must be a map of options.
The Loqate options you're trying to put have an incorrect format. Follow the guidelines about Loqate functions and fix errors (see more in Address Cleansing Properties).
MATCH_RULE_ATTRIBUTE_NOT_DEFINED_IN_SURROGATE_CROSSWALK Error Code 371

Error Message All the attributes that are used in the match rule must be defined in the surrogate crosswalk; unused attributes are attributes.

Detailed Error Message All the attributes that are used in the match rule must be defined in the surrogate crosswalk; unused attributes are attributes. Please add them to the surrogate crosswalk.
If a tenant configuration has the checkForMatchRuleAttrsInSurrogateCrosswalk property = true, there is a requirement for all attributes from match rules being described in the surrogate crosswalk section. Add the referred attribute to the surrogate crosswalk section for the modified entity type or don't use this attribute in match rules.
NO_MATCH_RULES_DEFINED_FOR_MATCH_GROUP Error Code 373

Error Message No match rules defined for match group uri.

Detailed Error Message No match rules defined for match group uri. Please define match rules.

Match group defined in the configuration does not have any match rules/negative match rules defined. Define match rules/negative match rules for the match group in the configuration, or remove the invalid match group from the configuration.
ATTRIBUTE_TYPE_IS_NOT_SIMPLE Error Code 375

Error Message Only simple type attributes are allowed in match rules.

Detailed Error Message Match rule rule_uri attribute attribute_uri must not have a type other than simple.
The attribute mentioned in the match rule is not of simple metadata type. Either avoid usage of the attribute, or change its metadata type to simple.
MATCH_CLASS_DOES_NOT_ACCEPT_PARAMETERS Error Code 376

Error Message Match class does not accept parameters.

Detailed Error Message Match rule: <rule>. Mapping: <mapping>

Occurs when trying to pass parameters to a match class that does not accept parameters. Make sure parameters configuration is aligned with the match class input parameters reference. For more information, see The Match Groups Construct.
WRONG_MATCH_RULE_PARAMETER Error Code 378

Error Message Match rule has wrong parameter.

Detailed Error Message Match rule <rule> has wrong parameter <name> with value <value>
Occurs when passed parameter does not satisfy the rule constraints/requirements (for example, match rule weight is negative). Make sure parameters configuration is aligned with the match class input parameters reference. For more information, see The Match Groups Construct.
RELEVANCE_BASED_RULE_HAS_MUTUALLY_EXCLUSIVE_THRESHOLDS Error Code 379

Error Message Relevance based rule cannot have not-a-match threshold along with suspect or auto thresholds.

Detailed Error Message Match rule: <rule>
Occurs when the relevance based rule has a not match threshold along with the auto and/or suspect threshold. This serves a specific requirement for relevance based rules implementation. Preserve either not match threshold or the threshold of the auto and/or suspect rules.
MATCH_OR_KEY_FIELD_ATTRIBUTE_NOT_SIMPLE Error Code 383

Error Message Some attribute URIs used in the keyAttributeURIs/matchFieldURIs are not simple type in the attribute {1}.

Detailed Error Message Only a simple type attribute URI can be used in keyAttributeURIs/matchFieldURIs. In the nested attribute {1}, 3Attributes URIs {0} set in keyAttributeURIs/matchFieldURIs are not simple type attributes.
If the keyAttributeURIs/matchFieldURIs section uses nested or reference attribute URIs. Remove non-simple attributes from the keyAttributeURIs/matchFieldURIs section.
CLEANSE_FUNCTION_VALIDATION_ERROR Error Code 714

Error Message Cleanse function CleanseFunctionName validation error.

Detailed Error Message Validation of cleanse function cleanseFunctionName failed with an error: error details.
An error occurred during the creation of the described cleanse function. If details in the error message do not clarify the reason for the error, contact the Reltio Customer Support team.
CLEANSE_MAPPING_ATTRIBUTE_NOT_FOUND Error Code 715

Error Message Cleanse mapping contains a non-existent attribute.

Detailed Error Message Cleanse mapping with URI uri contains a non-existent attribute attribute uri.
A cleanse function mapping refers to an attribute that does not exist in the entity type. Use a correct attribute name in the mapping.
CLEANSE_FUNCTION_MISSING_ATTRIBUTE Error Code 718

Error Message Required attributeName attribute value missing in cleanse.

Detailed Error Message Required value for attributeName attribute is missing for the cleanse URI uri.
Cleanse function is not set in the configuration for the cleanser. Set the name of the required cleanse function.
CLEANSE_FUNCTION_INPUT_MAPPING_MISSING Error Code 719

Error Message Input mapping missing for cleanse function CleanseFunctionName.

Detailed Error Message Input mapping is not defined for the cleanse function cleanseFunctionName. Add the cleanse function mappings fields such as inputMapping or inputMappingRef.
Cleanse function section does not have any information about the input mappings. Add the cleanse function mappings fields, such as inputMapping and inputMappingRef. For more information, see Configuring Cleanse Rules.
CLEANSE_FUNCTION_OUTPUT_MAPPING_MISSING Error Code 720

Error Message Output mapping missing for cleanse function CleanseFunctionName.

Detailed Error Message Output mapping is not defined for the cleanse function CleanseFunctionName. Add the cleanse function mappings fields such as outputMapping or outputMappingRef.
Cleanse function section does not have any information about the output mappings. Add the cleanse function mappings fields, such as outputMapping and, outputMappingRef. For more information, see Configuring Cleanse Rules.
UNKNOWN_CLEANSE_FUNCTION_ERROR Error Code 721

Error Message Cleanse function cleanseFunctionName not defined.

Detailed Error Message Cleanse function cleanseFunctionName is not defined in the tenant storage configuration (uri: uri).
You are trying to use a cleanse function that is not available or not defined in the physical configuration of the tenant. Add a definition of the cleanse function to the tenant physical configuration (in the cleanse section).
CLEANSE_FUNCTION_INVALID_OPTION_VALUE Error Code 722

Error Message Cleanse function cleanseFunctionName has invalid option/parameter value.

Detailed Error Message Cleanse function cleanseFunctionName has an invalid value GivenValue for the parameter OptionName, the allowed values are: AllowedValues.
When an incorrect value is provided for a cleanser parameter/option. For example, a non-Boolean value is provided for the option ovOnly. Update the option with the correct value or remove the property from the parameters section.
CLEANSE_FUNCTION_INVALID_OPTION Error Code 723

Error Message Cleanse function cleanseFunctionName has invalid parameter.

Detailed Error Message Unknown parameter param found in thecleanseFunctionName cleanse function in the tenant/business model configuration.
You are trying to use an option that is unknown to the defined cleanse function. Use the proper values from the options available for the different cleansers.
CLEANSE_FUNCTION_URL_ERROR Error Code 724

Error Message Cleanse function cleanseFunctionName has invalid URL.

Detailed Error Message Cleanse function cleanseFunctionName has an incorrect URL: URL. Provide the URL in the correct format.
(For HTTP cleanse function only) You are trying to use an incorrect URL for the HTTP function. Provide the URL in the correct format.
CLEANSE_FUNCTION_INVALID_S3_BUCKET Error Code 725

Error Message Cleanse function cleanseFunctionName has invalid S3. bucket name

Detailed Error Message S3 bucket BucketName defined in the cleanse function cleanseFunctionName was not found.
(For S3File cleanse function only) You are trying to use an S3 bucket that does not exist. Use the correct S3 bucket.
CLEANSE_FUNCTION_INVALID_S3_FILE Error Code 726

Error Message Cleanse function cleanseFunctionName has invalid S3 path.

Detailed Error Message Cleanse function cleanseFunctionName has an invalid S3 path: FilePath. Use a correct file from the given S3 bucket.
(For S3File cleanse function only) You are trying to use a file that does not exist in the given S3 bucket. Use the correct file from the given S3 bucket.
CLEANSE_FUNCTION_MISSING_REQUIRED_OPTION Error Code 727

Error Message Required parameter missing for cleanse function cleanseFunctionName.

Detailed Error Message Cleanse function cleanseFunctionName does not have the required parameter: ParamName.
Required parameters are missing in the cleanse function. Provide the required parameters
CLEANSE_FUNCTION_INVALID_INPUT Error Code 728

Error Message Cleanse function cleanseFunctionName has invalid input cleanse attribute.

Detailed Error Message Cleanse function cleanseFunctionName has an unknown input cleanseAttribute value value.
You are trying to use an input attribute that is not supported by the cleanser. Use a valid input attribute supported by the cleanser.
CLEANSE_FUNCTION_INVALID_OUTPUT Error Code 729

Error Message Cleanse function cleanseFunctionName has invalid output cleanse attribute.

Detailed Error Message Cleanse function cleanseFunctionName has an unknown output cleanseAttribute value value.
You are trying to use an output attribute that is not supported by the cleanser. Use a valid output attribute supported by the cleanser.
INVALID_LIFECYCLE_ACTION_URI Error Code 959

Error Message Lifecycle Action URI uri is invalid.

Detailed Error Message Lifecycle Action URI uri is invalid.
A uri of an LifeCycle Action has an incorrect format. Use the correct format of the uri (see more LCA Configuration).
LIFE_CYCLE_OPERATION_ERROR Error Code 1004

Error Message Error occurred in Life Cycle Action Validation: unknown hook name name.

Detailed Error Message Error occurred in Life Cycle Action Validation: unknown hook name name.
A Life Cycle Group uses an unknown hook name. Change the hook name to an existing one (see more in LCA Hooks).
LIFE_CYCLE_OPERATION_ERROR Error Code 1004

Error Message Error occurred in Life Cycle Action Validation: filter expression value parsed with an error.

Detailed Error Message Error occurred in Life Cycle Action Validation: filter expression value parsed with an error.
A filter field inside a Life Cycle Group definition has an incorrect format. Use the correct format of the expression (see more in Conditional Execution of LCA).
LIFE_CYCLE_OPERATION_ERROR Error Code 1004

Error Message Error occurred in Life Cycle Action Validation: wrong answer from the Amazon Lambda for name action. Make sure that protocol name protocol is proper for it.

Detailed Error Message Error occurred in Life Cycle Action Validation: wrong answer from the Amazon Lambda for name action. Make sure that protocol name protocol is proper for it.
An Lambda Action that is mentioned in an action list resulted in the wrong format answer during its checking at the Amazon Lambda service. It usually means that a user is trying to define a Lambda action as a BinaryJSON instead of the default format or vice versa. Try to change the action name from Lambda/Name to Lambda/BinaryJSON/Name or vice versa (see more in LCA Configuration). If this doesn't help, please contact support.
LIFE_CYCLE_OPERATION_ERROR Error Code 1004

Error Message Error occurred in Life Cycle Action Validation: checking of name action failed (see the details).

Detailed Error Message Error occurred in Life Cycle Action Validation: checking of name action failed (see the details).
An error has occurred during checking of a mentioned Lambda Action at the Amazon Lambda service. If the details in the message do not clarify the reason of the error, please contact support.
LIFE_CYCLE_OPERATION_ERROR Error Code 1004

Error Message Error occurred in Life Cycle Action Validation: action with name name is not active on Lifecycle server.

Detailed Error Message Error occurred in Life Cycle Action Validation: action with name name is not active on the Lifecycle server.
You're trying to use an action that is not active on the Lifecycle Service. Mark the lifecycle action as active on the Lifecycle Service, or use another action in the configuration.
LIFE_CYCLE_OPERATION_ERROR Error Code 1004

Error Message Error occurred in Life Cycle Action Validation: action names names do not exist on Lifecycle server

Detailed Error Message Error occurred in Life Cycle Action Validation: action names names do not exist on the Lifecycle server.
You're trying to use an action that doesn't exist on the Lifecycle Service. Register the lifecycle action with this name on the Lifecycle Service, or use another action in the configuration.
LIFE_CYCLE_OPERATION_ERROR Error Code 1004

Error Message Error occurred in Life Cycle Action: lifecycle service URI is not configured for tenant name.

Detailed Error Message Error occurred in Life Cycle Action: lifecycle service URI is not configured for tenant name.
For using Life Cycle Actions the Lifecycle Service must be registered. Register a URI of the Lifecycle Service in the tenant physical configuration (lifecycleActionsService field).
INVALID_CARDINALITY_MIN_VALUE Error Code 1006

Error Message Invalid minValue cardinality for attribute with attribute URI uri

Detailed Error Message minValue cardinality cannot be less than 0 (zero).
A cardinality section has a minValue field with a value less than 0(zero). Change the value to a correct one or remove the field.
INVALID_CARDINALITY_MAX_VALUE Error Code 1007

Error Message Invalid maxValue cardinality for attribute with attribute URI uri.

Detailed Error Message maxValue cardinality cannot be less than 1.
A cardinality section has a maxValue field with a value less than 1. Change the value to a correct one or remove the field.
INVALID_CARDINALITY_VALUES Error Code 1008

Error Message Invalid combination of minValue and maxValue cardinality for attribute with attribute URI uri.

Detailed Error Message maxValue cardinality cannot be less than minValue cardinality.
A cardinality section has a maxValue field with a value less than a minValue field from the same section. Change the values to the correct ones or remove the unnecessary fields.
INVALID_DEFAULT_VALUE Error Code 1009

Error Message Invalid default value for attribute with attribute URI uri.

Detailed Error Message The default value type must match the attribute type.
A value that is set in a defaultValue field is a mismatch for an attribute value type (not a number for integer, not a date for date, and so on.). Either fix the incorrect value, or remove the default value field, or change the attribute type if it's incorrect.
ATTRIBUTE_NAME_DOESNT_MATCH_URI Error Code 1811

Error Message Attribute name in URI does not equal to value of "name" field from configuration.

Detailed Error Message Last part of URI string does not equal to value of "name" field from configuration.
There is discrepancy between the attribute name and the URI fields. Correct the attribute name or last part of attribute URI to make them equal.
METADATA_SURVIVORSHIP_GROUP_MAPPINGS_INVALID_SORT_AS Error Code 1812

Error Message The sortAs parameter has not allowed value.

Detailed Error Message The 'sortAs' parameter has not allowed value, current value = {0}, allowed values = {1}. Please fix the mapping for the attribute {2}' of survivorship group {3}.
The sortAs parameter value is invalid. From the error message, use of any of the values listed in the allowed list as SortAs parameter.
METADATA_SURVIVORSHIP_GROUP_SORT_AS_IN_NOT_MIN_MAX_STRATEGY Error Code 1813

Error Message The sortAs parameter set for not allowed strategy.

Detailed Error Message The sortAs parameter not allowed in {0} strategy. It is allowed only in MinValue/MaxValue strategies. Please fix the mapping for the attribute {1} of survivorship group {2}.
The SortAs parameter is allowed only for Min and Max values in OV strategies. Do not use SortAs parameters in OV strategies that are not of Min or Max values.
MAX_REFERENCE_ATTRIBUTE_PER_ENTITY_LIMIT_EXCEEDED Error Code 1900

Error Message Number of reference attributes in a single entity record type must not exceed value.

Detailed Error Message Number of reference attributes in a single entity record type must not exceed value, but the current number is value. Please reduce the number of reference attributes for the entity.
The tenant physical configuration has a restriction on a maximum amount of referenced attributes for an entity type. The current amount for the entity type exceeds this number. Either remove some referenced attributes to fit the restriction number, or increase the restriction number in the tenant physical configuration (dataModelerConstraints/maxReferenceAttributesCount field), or remove the restriction. For more information, see Validation Constraints for a Tenant.
NO_DATATYPE_CHANGE_FOR_INHERITED_ATTRIBUTES Error Code 1905

Error Message Data type changed for the inherited attribute name for entity type with parent type type from type value to type value.

Detailed Error Message The data type changed for the inherited attribute name for entity type with parent type type from type value to type value. Data type changes are not allowed for inherited attributes. Please correct the data types.
The tenant physical configuration prohibits overriding of an attribute type from a parent entity type in an inherited one. Some attribute violates this restriction. Either change the attribute type in the inherited attribute to the same type as a parent attribute has, or disable the restriction in the tenant physical configuration (dataModelerConstraints/allowDataTypeOverRiding field). For more information, see Validation Constraints for a Tenant.
DUPLICATE_URIS_FOR_TYPE Error Code 1907

Error Message There are duplicate URIs [uri_list] in mapping for the type [type].

Detailed Error Message There are duplicate URIs [uri_list] in mapping for the type [type]. Please remove duplication.
The business configuration for object type (entities, relations) contains two or more definitions of an attribute with the same uri. Remove duplicate definitions from the configuration.
USE_ONLY_OV_VALUES_AND_IGNORE_NON_OV_CHANGES_FLAGS_ARE_INCOMPATIBLE Error Code1909

Error Message For type entity type, useOnlyOvValuesInReferencedEntities is set to true, but ignoreNonOVChangesWhenUpdateThroughReferencedEntity is false.

Detailed Error Message For type entity type, useOnlyOvValuesInReferencedEntities is set to true, but ignoreNonOVChangesWhenUpdateThroughReferencedEntity is false.
For the entity type in the business configuration, it is forbidden to have the 'ignoreNonOVChangesWhenUpdateThroughReferencedEntity' property as false when the 'useOnlyOvValuesInReferencedEntities' property is enabled. Set 'ignoreNonOVChangesWhenUpdateThroughReferencedEntity' to true or set 'useOnlyOvValuesInReferencedEntities' to false.
PRIMARY_ATTRIBUTE_NOT_SPECIFIED_FOR_OTHER_ATTRIBUTE_STRATEGY Error Code 1910

Error Message For the attribute attribute in tenant name, the survivorship strategy is OtherAttributeWinnerCrosswalk, but the strategy's required attribute primaryAttributeUri isn't specified.

Detailed Error Message For the attribute attribute in tenant name, the survivorship strategy is OtherAttributeWinnerCrosswalk, but strategy's required attribute primaryAttributeUri isn't specified.
If OtherAttributeWinnerCrosswalk is used, primaryAttributeUri in a mapping must also be specified. Add primaryAttributeUri to the attribute's survivorship mapping.
DUPLICATE_SURVIVORSHIP_STRATEGY Error Code 1912

Error Message Survivorship strategy strategy name is defined multiple times.

Detailed Error Message survivorshipStrategies contains multiple definitions of the {0} strategy; therefore, please remove duplicates.
There are multiple definitions of the same survivorship strategy in the survivorshipStrategies section of the business configuration. Remove definition duplicates.
METADATA_WRONG_SURVIVORSHIP_STRATEGY_DEFINITION Error Code 1913

Error Message Survivorship strategy strategy name has incorrect definition.

Detailed Error Message It's impossible to determine a strategy type for the strategy 'strategy name. If it's a custom strategy, please specify the required fields (parentStrategyURI or mainSourceType and winnerSourceType).
The survivorship strategy has an incomplete definition.

There are two possible custom strategies in an OV configuration, and you must specify required fields for one of them.

  • Record-values based source priority. Required field: winnerSourceType.
  • Custom survivorship strategy. Required fields: parentStrategyURI and mainSourceType.
CIRCULAR_DEPENDENCIES_IN_SURVIVORSHIP_RULES Error Code 1914

Error Message Circular dependency has been found in survivorship rules for entity type/configuration.

Detailed Error Message Circular dependency has been found in survivorship rules for entity type/configuration at primaryAttributeUris in group (complex source strategies) (path of dependency: dependency chain).
A circular dependency has been found in the OV configuration for two particular cases:
  • OtherAttributeWinnerCrosswalk strategy has primaryAttributeUris fields which refer to other attributes, and this reference chain creates a circular dependency.
  • Custom survivorship strategy has parentStrategyURI fields which refer to other strategies, and this reference chain creates a circular dependency.
Remove duplicate dependencies from the configuration, and set up the correct references.
SURVIVORSHIP_SOURCE_NOT_FOUND Error Code 1915

Error Message Source type source mentioned in the survivorship rules configuration does not exist.

Detailed Error Message Business model for the tenant does not have the source source system that is mentioned in section for object type.
A source system that is mentioned in an OV configuration is not defined in the business configuration. Remove the incorrect reference to the non-existent source type from the section, or add a definition of that system in the sources section of the business configuration.
INCORRECT_ATTRIBUTE_URI_IN_OV_CONFIGURATION Error Code 1916

Error Message Attribute with URI attribute mentioned in survivorship rules configuration is not found.

Detailed Error Message The attribute with URI configuration mentioned in section doesn't exist or the URI has an invalid format.

One of the parts of an OV configuration refers to an attribute that doesn't exist.

Another option is that the uri has an incorrect format (does not start from configuration/entityTypes/... or configuration/relationTypes/..., or perhaps this is another option).

Remove the reference to the non-existent attributes, or correct its uri if the attributes exists.
DUPLICATE_SURVIVORSHIP_GROUP Error Code 1917

Error Message Survivorship group uri is defined multiple times.

Detailed Error Message Type object type contains multiple definitions of the group uri survivorship group; therefore, please remove duplicates.
One of the survivorship groups with the same uri is defined multiple times. Remove the duplicates, or change their uris.
DUPLICATE_ROLES_IN_SURVIVORSHIP_GROUP Error Code 1918

Error Message Role role is mentioned multiple times in survivorship groups of object type.

Detailed Error Message Role role is mentioned multiple times in survivorship groups uris. Please leave only one reference to the role.
One of the roles is mentioned in different survivorship groups for the same entity/relation types, which is forbidden. A role can be applied and used only in the single group; otherwise, it's not clear what group must be used for a user with this role. Leave only one reference of the role in the survivorship groups for this entity/relation type.
MULTIPLE_DEFAULT_SURVIVORSHIP_GROUPS Error Code 1919

Error Message Type 'type' has multiple default survivorship groups.

Detailed Error Message Type 'type' has multiple default survivorship groups, only one is allowed. Please set ''default = false'' for not-default groups.
More than one survivorship group is marked as default in an OV configuration. Leave only one default survivorship group, mark the others as 'default = false'.
UNKNOWN_FIELD_IN_OV_CONFIGURATION Error Code 1920

Error Message Field name must not be specified for strategy strategy name.

Detailed Error Message Field name must not be specified for strategy strategy name in place because it's not used.
One of survivorship mappings has a field which, in fact, is not used, because either a related strategy doesn't support it, or a place in which this field is specified is not correct. Remove the unused field from the configuration, or change the survivorship strategy to the one that supports that field.
PRIMARY_ATTRIBUTE_IS_SUBATTRIBUTE Error Code 1921

Error Message Primary attribute uri is a sub-attribute for parent uri in survivorship mapping.

Detailed Error Message The attribute uri is mentioned as a primary for its parent attribute parent uri in its survivorship mapping. This configuration is forbidden.
A mapping with OtherAttributeWinnerCrosswalks strategy has a primary attribute that refers to the mapping attribute’s sub-attribute. The calculation algorithm for this configuration is not clear, and that's why it's forbidden. Change primaryAttributeUri for this mapping to another one that is not at a sub-level, or change the strategy from OtherAttributeWinnerCrosswalks to something else.
METADATA_COMPARISON_ATTRIBUTE_FOR_SIMPLE Error Code 1922

Error Message Survivorship group mapping is incorrect for attribute in survivorship group id.

Detailed Error Message comparisonAttributeUri must not be used for a simple attribute uri, which is used in mapping group id.
A mapping for a simple attribute has the comparisonAttributeUri field. However, this field is not required because a strategy can use a value from an attribute itself. Remove comparisonAttributeUri from the mapping.
INVALID_PROPERTY_VALUE Error Code 1923

Error Message Value value for the property property is invalid.

Detailed Error Message The definition of the property property is invalid. The reason is reason.
The value for the global property pinIgnoredOverridePriority has the wrong definition. It must have an array as the value with exactly the items: "pin", "ignored", "neutral" in any desired order.

Remove the definition from the configuration. You must use the default value ["pin", "ignored", "neutral"].

Specify the correct value, for example, ["ignored", "pin", "neutral"].

DUPLICATE_MATCH_GROUP Error Code 1924

Error Message Match group matchGroupURI is defined multiple times

Detailed Error Message Type type contains multiple definitions of matchGroupURI match group, please remove duplicates.
The business configuration for object type contains two or more definitions of a match group with the same uri. Remove duplicate definitions of match groups from the configuration.
INVALID_RELATIONSHIP_START_OBJECT Error Code 1951

Error Message No start object defined for relationship 'uri'

Detailed Error Message Invalid start object configuration for relationship 'uri'. Please provide a valid relationship start object with uri.
Relationship must have a valid start object configuration defined with a valid object type uri. Define a valid start object for relationship type with a valid object type uri referring to a entity.
INVALID_RELATIONSHIP_END_OBJECT Error Code 1952

Error Message No end object defined for relationship 'uri'.

Detailed Error Message Invalid end object configuration for relationship 'uri'. Please provide a valid relationship end object with uri.
Relationship must have a valid end object configuration defined with a valid object type uri. Define a valid end object for relationship type with a valid object type uri referring to a entity.
METADATA_ATTRIBUTE_WITH_DIFFERENT_TYPES Error Code 1960

Error Message Attribute attribute has different types across different entity/relation types.

Detailed Error Message The value types that are presented in attribute uri are not compatible. Please change one of the following types or rename their attribute: object and attribute types list.

According to ES's restrictions, all attributes that have the same name (including sub-nested ones, for example, Identifiers/ID) must have the same (or compatible) value types across all entity/relation types in a configuration. Currently, one of the attributes with the same name has an incompatible value type.

Compatible types: text data (String, Blob), time (Date, Time, Timestamp), numbers without fractional components (Long, Int, Integer), and fractional numbers (Float, Double, Number).

Note: If the configuration you're trying to post doesn't have any conflicts, it probably means that the attribute with different types was inherited from verticals. Take a look at the details in the error message.

Change the value type in one of the attributes to a compatible one, or rename the attribute uri for the attributes with conflicts.

For more information, see Validation Error Code 1960.

Note: This change can require data migration for existent tenants. Please discuss it with PM/RM teams. When this work is done, remember to run the Reindex task.
METADATA_CLEANSE_CROSSWALK_AS_SURROGATE Error Code 1961

Error Message Cleanse crosswalk source uri is configured as a surrogate crosswalk in entity type type.

Detailed Error Message It is not allowed to specify in the surrogateCrosswalks section the crosswalk source system that is used in cleanse for the same entity type.
The surrogate crosswalks section contains the definition for a source type that is used in cleansing. Remove the cleanser source type definition from the surrogate crosswalks section.
METADATA_SOURCE_SYSTEM_NOT_FOUND Error Code 1962

Error Message Source type source uri does not exist.

Detailed Error Message The business model for the tenant doesn't have the uri source system that is mentioned in place for type uri.
One of configuration parts has a reference to a source system that is not defined. Add a definition for the absent source system or remove the reference to it.
METADATA_DUPLICATE_DEFINITIONS Error Code 1963

Error Message There are multiple definitions of uri in place.

Detailed Error Message Place contains multiple definitions of uri, please remove duplicates
One of configuration parts has a duplicate definition of some object; for example, the same attribute in the referencedAttributeUris configuration. Remove the duplicates.
METADATA_SAME_RELATION_IN_REFERENCED_ATTRIBUTES Error Code 1964

Error Message Relation type type is used in multiple referenced attributes for object type.

Detailed Error Message It is forbidden to have the same relation type in more than one referenced attribute. For object type relation type, type is used in attributes.
One of relation types is used more than once in reference attributes for some entity type. One relation type can represent only one reference attribute per type. Remove the duplicated reference attribute, or introduce a new relation type (which can extend the first one with all the fields), and set it to the duplicated reference attribute.
METADATA_SUB_REFERENCE_IN_SURROGATE_CROSSWALKS Error Code 1965

Error Message Sub-reference attribute uri is mentioned in the surrogateCrosswalk section.

Detailed Error Message It is forbidden to use a sub-reference attribute for surrogate crosswalks.
The surrogate crosswalks section contains a sub-reference attribute in its attribute list. Remove the sub-reference attribute from the surrogateCrosswalks section.
METADATA_SUB_REFERENCE_IN_SURVIVORSHIP_MAPPING Error Code 1966

Error Message Sub-reference attribute uri is mentioned in survivorship mapping for object type.

Detailed Error Message It is forbidden to define survivorship rules for sub-reference attributes.
An attribute mapping for a sub-reference attribute is specified. This mapping is forbidden, because the OV for sub-reference attributes is calculated by rules of the reference attribute's related entity type/relation types. Remove the sub-reference attribute mapping from the configuration.
METADATA_SECTION_IS_EMPTY Error Code 1967

Error Message Required section name is empty in place for object type.

Detailed Error Message It is required to have the non-empty field name in place.
One of the required fields has an empty list of values; for example, in an attributes list in the surrogateCrosswalks section) Add values to the required list.
REFERENCE_ATTRIBUTE_REFERENCED_ENTITY_TYPE_MISSED Error Code 1970

Error Message Reference attribute specification for {0} has no referenced entity type URI.

Detailed Error Message Configuration has no reference entity type URI for the reference attribute {0}. Please add the suitable URI using the referencedEntityTypeURI field.
   
REFERENCE_ATTRIBUTE_RELATIONSHIP_TYPE_MISSED Error Code 1971

Error Message Relationship type is missed in the {0} reference attribute specification.

Detailed Error Message Configuration has no relationship type URI for the reference attribute {0}. Please add the suitable URI using the relationshipTypeURI field.