Vertical Errors

Learn about the errors that must be fixed in Reltio business configuration.

This page lists the various errors that were found in Reltio business configuration for the following two verticals and were fixed:
  • configuration/_vertical/life-sciences
  • configuration/_vertical/reltio-configuration

Fix for 2019.2

This section describes the set of error codes that were fixed for the release version 2019.2 and the impact of the provided fix.

uri:configuration/_vertical/reltio-core-2019-2 (uri:configuration/_vertical/reltio-configuration with the new changes)

"errorCode": 1916

{
  "severity": "Error",
  "errorMessage": "Attribute with URI 'configuration/entityTypes/Location/attributes/State' mentioned in survivorship rules configuration is not found",
  "errorCode": 1916,
  "errorDetailMessage": "The attribute with URI 'configuration/entityTypes/Location/attributes/State' mentioned in configuration/entityTypes/Location doesn't exist or the URI has an invalid format"
}

Details of the fix - As a part of this fix, the default mapping for Location was changed and configuration/entityTypes/Location/attributes/State was removed from the mapping. It is possible that the Operational Value (OV) calculations for configuration/entityTypes/Location/attributes/State and configuration/entityTypes/Location/attributes/StateProvince are changed.

Impact of the provided fix

  • If you were using the removed attribute configuration/entityTypes/Location/attributes/State, then check the survivorship rules related to this change. Following are the points that you must check:
    • If the change affected the inherited metadata configuration of the survivorship rule and that rule was removed, then review the rule and add the survivorship rule back through your L3 configuration.
    • If the change did not affect the inherited metadata configuration of the survivorship rule, then you need not make any further changes.
  • If you were not using the removed attribute configuration/entityTypes/Location/attributes/State, then check your L3 configuration to confirm that you are not using that attribute in your survivorship group.
uri:configuration/_vertical/life-sciences-2019-2 (uri:configuration/configuration/_vertical/life-sciences with the new changes)

Details of the fix - As a part of this fix, the incorrect path for the GSASanction attribute was corrected.

Before the fix

configuration/entityTypes/GSASanction/...

Corrected after the fix

configuration/entityTypes/HCP/attributes/GSASanction/...

Impact of the provided fix - This fix does not require you to make any changes.

"errorCode": 1916

{
  "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"
}

Details of the fix - As a part of this fix, the default mapping for HCP was changed. configuration/entityTypes/HCP/attributes/Degree attribute was not configured in our verticals and therefore it has been removed.

Impact of the provided fix

  • If you were using the removed attribute configuration/entityTypes/HCP/attributes/Degree, then check the survivorship rules related to this change. Following are the points that you must check:
    • If the change affected the inherited metadata configuration of the survivorship rule and that rule was removed, then review the rule and add the survivorship rule back through your L3 configuration.
    • If the change did not affect the inherited metadata configuration of the survivorship rule, then you need not make any further changes.
  • If you were not using the removed attribute configuration/entityTypes/HCP/attributes/Degree, then check your L3 configuration to confirm that you are not using that attribute in your survivorship group.

"errorCode": 342

[
  {
    "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"
  },
  {
    "severity": "Error",
    "errorMessage": "Attribute with URI 'configuration/relationTypes/HasAddress/attributes/RankConfidence' mentioned in GPO 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"
  },
  {
    "severity": "Error",
    "errorMessage": "Attribute with URI 'configuration/relationTypes/HasAddress/attributes/CDS' mentioned in IDN is not defined",
    "errorCode": 342,
    "errorDetailMessage": "The attribute with URI 'configuration/relationTypes/HasAddress/attributes/CDS' mentioned in referencedAttributeURIs of Address doesn't exist in HasAddress or the URI has an invalid format"
  },
  {
    "severity": "Error",
    "errorMessage": "Attribute with URI 'configuration/relationTypes/HasAddress/attributes/CDS' mentioned in GPO is not defined",
    "errorCode": 342,
    "errorDetailMessage": "The attribute with URI 'configuration/relationTypes/HasAddress/attributes/CDS' mentioned in referencedAttributeURIs of Address doesn't exist in HasAddress or the URI has an invalid format"
  },
  {
    "severity": "Error",
    "errorMessage": "Attribute with URI 'configuration/relationTypes/HasAddress/attributes/AddressBestVisit' mentioned in IDN is not defined",
    "errorCode": 342,
    "errorDetailMessage": "The attribute with URI 'configuration/relationTypes/HasAddress/attributes/AddressBestVisit' mentioned in referencedAttributeURIs of Address doesn't exist in HasAddress or the URI has an invalid format"
  },
  {
    "severity": "Error",
    "errorMessage": "Attribute with URI 'configuration/relationTypes/HasAddress/attributes/AddressBestVisit' mentioned in GPO is not defined",
    "errorCode": 342,
    "errorDetailMessage": "The attribute with URI 'configuration/relationTypes/HasAddress/attributes/AddressBestVisit' mentioned in referencedAttributeURIs of Address doesn't exist in HasAddress or the URI has an invalid format"
  }
]

Details of the fix - As a part of this fix, non-defined attributes were removed from the referencedAttributeURIs array.

Impact of the provided fix

  • If the non-defined attributes were present in the L3 configuration, then return such attributes through the L3 configuration (referencedAttributeURIs). In this scenario, if referencedAttributeURIs is not removed from the L3 configuration, then that reference attribute disappears from the system and the data stored in the attribute is lost.
  • If the non-defined attributes were not present in the L3 configuration, it means that the attributes were never used and therefore you need not make any further changes.

"errorCode": 1960

{
  "severity": "Error",
  "errorMessage": "Attribute FoundedYear has different types across different entity/relation types",
  "errorCode": 1960,
  "errorDetailMessage": "The value types that are presented in attribute FoundedYear are not compatible. Please change one of the following types or rename their attribute: Int (HCO, Company, Organization), String (IDN, GPO)"
}

Details of the fix - As a part of this fix, the attribute type of the FoundedYear attribute was changed from String to Int, for the IDN and GPO entity types.

Impact of the provided fix

  • If you were using the FoundedYear attribute and if all the data cannot be covered as Int type, then you must check for the following points:
    • All the attributes must be changed to String type so that the attributes are properly indexed in the L3 configuration.
    • Run the reindex task with reindex?updateEntities=true.
  • If you were using the FoundedYear attribute and if all the data are covered as Int type, then run the reindex task with reindex?updateEntities=true.
  • If you were earlier using the FoundedYear attribute but now you do not have any data for that attribute, then check if the attribute was indexed in the correct way.
  • If you have never used the FoundedYear attribute, then you need not make any further changes.

Fix for 2020.1

This section describes the set of error codes that were fixed for the release version 2020.1 and the impact of the provided fix.

uri:configuration/_vertical/reltio-core-2020-1 (uri:configuration/configuration/_vertical/reltio-core-2019-2 with the new changes)

"errorCode": 1960

"configuration": {
        "warnings": [
            {
                "severity": "Error",
                "errorMessage": "Attribute Ticker has different types across different entity/relation types",
                "errorCode": 1960,
                "errorDetailMessage": "The value types that are presented in attribute SIMPLE:[configuration/entityTypes/GPO/attributes/Ticker, configuration/entityTypes/IDN/attributes/Ticker] are not compatible. Please change one of the following types or rename their attribute: NESTED:[configuration/entityTypes/HCO/attributes/Ticker, configuration/entityTypes/Company/attributes/Ticker]"
            }
        ]
    }

Details of the Fix - As a part of this fix, the nested attribute uri:configuration/entityTypes/Organization/attributes/Ticker was removed from the vertical.

Impact of the provided fix

  • If you were using the nested attribute uri:configuration/entityTypes/Organization/attributes/Ticker, then ensure to add the attribute description into your L3 configuration. Otherwise, this may lead to data loss.
  • If you were not using the nested attribute uri:configuration/entityTypes/Organization/attributes/Ticker, then you need not make any further changes.
uri:configuration/_vertical/reltio-life-sciences-2020-1 (uri:configuration/configuration/_vertical/life-sciences-2019-2 with the new changes)

"errorCode": 1811

{
    "configuration/relationTypes/GPOtoHCO/attributes/ID": {
        "warnings": [
            {
                "severity": "Error",
                "errorMessage": "Attribute name 'GPO' doesn't match with attribute uri 'configuration/relationTypes/GPOtoHCO/attributes/ID'",
                "errorCode": 1811,
                "errorDetailMessage": "Attribute name 'GPO' doesn't match with attribute uri 'configuration/relationTypes/GPOtoHCO/attributes/ID'"
            }
        ]
    },
    "configuration/relationTypes/GPOtoIDN/attributes/ID": {
        "warnings": [
            {
                "severity": "Error",
                "errorMessage": "Attribute name 'GPO' doesn't match with attribute uri 'configuration/relationTypes/GPOtoIDN/attributes/ID'",
                "errorCode": 1811,
                "errorDetailMessage": "Attribute name 'GPO' doesn't match with attribute uri 'configuration/relationTypes/GPOtoIDN/attributes/ID'"
            }
        ]
    },
    "configuration/interactionTypes/Email/attributes/WordsCount": {
        "warnings": [
            {
                "severity": "Error",
                "errorMessage": "Attribute name 'Subject' doesn't match with attribute uri 'configuration/interactionTypes/Email/attributes/WordsCount'",
                "errorCode": 1811,
                "errorDetailMessage": "Attribute name 'Subject' doesn't match with attribute uri 'configuration/interactionTypes/Email/attributes/WordsCount'"
            }
        ]
    },
    "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/relationTypes/ParentChild/attributes/ID": {
        "warnings": [
            {
                "severity": "Error",
                "errorMessage": "Attribute name 'IDN' doesn't match with attribute uri 'configuration/relationTypes/ParentChild/attributes/ID'",
                "errorCode": 1811,
                "errorDetailMessage": "Attribute name 'IDN' doesn't match with attribute uri 'configuration/relationTypes/ParentChild/attributes/ID'"
            }
        ]
    }
}

Details of the fix - As a part of this fix, the values of the name and label parameters in the attribute description were corrected.

The name IDN was incorrect as per uri:configuration/relationTypes/ParentChild/attributes/ID. The correction was made as shown below:

Before the fix

{
	"label": "IDN",
	"name": "IDN",
	"description": "",
	"type": "String",
	"hidden": false,
	"important": false,
	"system": false,
	"faceted": true,
	"searchable": true,
	"attributeOrdering": {
		"orderingStrategy": "LUD"
	},
	"uri": "configuration/relationTypes/ParentChild/attributes/ID",
	"skipInDataAccess": false
},
Corrected after the fix
{
	"label": "ID",
	"name": "ID",
	"description": "",
	"type": "String",
	"hidden": false,
	"important": false,
	"system": false,
	"faceted": true,
	"searchable": true,
	"attributeOrdering": {
		"orderingStrategy": "LUD"
	},
	"uri": "configuration/relationTypes/ParentChild/attributes/ID",
	"skipInDataAccess": false
},
Impact of the provided fix - This fix impacted the UI view as the label was changed. If you want to return to the previous label, then overwrite the changes in your L3 configuration.

"errorCode": 1960

"configuration": {
        "warnings": [
            {
                "severity": "Error",
                "errorMessage": "Attribute Ticker has different types across different entity/relation types",
                "errorCode": 1960,
                "errorDetailMessage": "The value types that are presented in attribute SIMPLE:[configuration/entityTypes/GPO/attributes/Ticker, configuration/entityTypes/IDN/attributes/Ticker] are not compatible. Please change one of the following types or rename their attribute: NESTED:[configuration/entityTypes/HCO/attributes/Ticker, configuration/entityTypes/Company/attributes/Ticker]"
            }
        ]
    }

Details of the Fix - As a part of this fix, the simple attributes uri:configuration/entityTypes/GPO/attributes/Ticker and uri:configuration/entityTypes/IDN/attributes/Ticker were removed from the vertical.

Impact of the provided fix

  • If you were using the removed simple attributes, then ensure to add the attribute description into your L3 configuration. Otherwise, this may lead to data loss.
  • If you were not using the removed simple attributes, then you need not make any further changes.