Finding and Resolving Business Configuration Errors

You can find and resolve validation errors in your business configuration.

Preparing the Configuration File

Before you point to the new verticals in your L3 configuration in the production environment, perform the following steps in your test environment:

  1. Get the metadata configuration without inheritance - configuration/_noInheritance).
  2. Prepare the metadata configuration file (.JSON) based on the changes in the new vertical.
  3. Change the reference attribute URI to point to the new vertical - referenceConfigurationURI: configuration/_vertical/reltio-life-sciences-2020-1.
  4. Apply the changes to your L3 configuration.

Find Validation Errors

To find validation errors, run the validation API as follows:

Request

POST {{envUri}}/reltio/api/{{tenantId}}/configuration/_validation?validationErrorLevel=all
Table 1. Parameters
Parameter Required Default Description
validationErrorLevel No all errors, warnings, or all: filter for the level of errors to be displayed in the output.

Response

A JSON object with errors and warnings.

Example Response

"configuration/entityTypes/IDN": {
       "errors": [
           {
               "severity": "Error",
               "errorMessage": "Attribute with URI 'configuration/relationTypes/HasAddress/attributes/RankConfidence' mentioned in IDN is not defined",
               "errorCode": 342,
               "errorDetailMessage": "The attribute with URI 'configuration/relationTypes/HasAddress/attributes/RankConfidence' mentioned in referencedAttributeURIs of Address doesn't exist in HasAddress or the URI has an invalid format"
         },
"configuration/entityTypes/HCP": {
        "errors": [
            {
                "severity": "Error",
                "errorMessage": "Attribute with URI 'configuration/entityTypes/HCP/attributes/Degree' mentioned in survivorship rules configuration is not found",
                "errorCode": 1916,
                "errorDetailMessage": "The attribute with URI 'configuration/entityTypes/HCP/attributes/Degree' mentioned in configuration/entityTypes/HCP doesn't exist or the URI has an invalid format"
            }
        ]
    },
"configuration/relationTypes/IDNtoGPO/attributes/ID": {
        "warnings": [
            {
                "severity": "Error",
                "errorMessage": "Attribute name 'GPO' doesn't match with attribute uri 'configuration/relationTypes/IDNtoGPO/attributes/ID'",
                "errorCode": 1811,
                "errorDetailMessage": "Attribute name 'GPO' doesn't match with attribute uri 'configuration/relationTypes/IDNtoGPO/attributes/ID'"
            }
        ]
    },
“configuration/entityTypes/Location": {
        "warnings": [
            {
                "severity": "Error",
                "errorMessage": "Number of reference attributes in a single entity record <type> should not exceed <value>.",
                "errorCode": 1900,
                "errorDetailMessage": "Number of reference attributes in a single entity record <type> should not exceed <value>, but the current number is <value>. Please reduce the number of reference attributes for the entity."
            }
        ]
    }
}

In the above example, the response contains the errors 342 and 1916, and warnings 1811 and 1900.

Note: Customers who are not using Reltio verticals, must create new verticals and migrate their tenants from the old verticals to the new ones.

Resolve Validation errors

Perform the following steps to resolve validation errors:

  1. Refer to the L3 Validation Errors topic to search for the error codes mentioned in the response.
  2. Read the complete details about the error which also includes information about how to resolve the error.
  3. Fix the error by making relevant changes to the L3 configuration.
  4. Optionally, you may have to run a periodic task to resolve an error.

List of L3 Validation Errors

For information about L3 validation errors and how to resolve them, see L3 Validation Errors.

Changes to Verticals

For information about the changes that have been made to the verticals, see Vertical Errors.