Why is the DnB enrichment failing with a "Invalid attribute format specification" error?

Question

We have encountered an issue where DUNS: 691619688 is available in D&B enrichment file but dnb connector has updated Reltio profile with 'Enrichment Error'. Refer the screenshots below.

The DnB job was executed on 31 July 2024 after 4 pm IST to enrich Reltio with DnB data, and the enrichment file was received at the AWS S3 bucket in the morning hours of 31 July 2024 IST. The DnB connector enrichment mapping and Reltio L3 config remained the same.

We saw the below error in the LogDNA.

• Aug 9 20:12:09dnb-connector-5688d78ccf-4zl8rdnb-connectorERROR{"event":"org_create","context":{"tenantId":"<tenantId>","environment":"eu-360","operationType":"bkg_mon","operationId":"5639489705738240","username":"<username>","dnbUsername":"<dnbUserName>"},"additionalFields":{"dunsnumber":"691619688","index":11,"error":"Invalid attribute format specification for configuration/entityTypes/B2BOrganization/attributes/KeyFinancialFiguresOverview/attributes/FinancialStatementToDate: Invalid attribute value specification for configuration/entityTypes/B2BOrganization/attributes/KeyFinancialFiguresOverview/attributes/FinancialStatementToDate","uri":"entities/0dRfZJA"}}

Answer

We look at the seed file for the DUNS number and we see the following definition

{
"financialStatementToDate": "2022-12", <<<<=======
"financialStatementDuration": null,
"informationScopeDescription": "Individual",
"informationScopeDnBCode": 9066,
"reliabilityDescription": "Estimated",
"reliabilityDnBCode": 9093,
"unitCode": "SingleUnits",
"accountantName": null,
"yearlyRevenue": [
{
"value": 25200000000,
"currency": "JPY"
},
{
"value": 181717200,
"currency": "USD",
"trend": []
}
]
}
],

If we look at the L3 configuration for the attribute, we see it is a Date type.

{

"label": "Financial Statement To Date",
"name": "FinancialStatementToDate",
"type": "Date",   <<<<<<<<<<<<<<<======================
"hidden": false,
"important": false,
"system": false,
"required": false,
"faceted": false,
"searchable": true,
"attributeOrdering": {
"orderingStrategy": "LUD"
},
"uri": "configuration/entityTypes/Parties/attributes/KeyFinancialFiguresOverview/attributes/FinancialStatementToDate",
"skipInDataAccess": false
},

The issue needs to be corrected using the correct date format. DnB sends only the month, and the Date type also requires the day in the month. So the customer can define (this came from business logic) if they want to add a specific day (could be 01 or 15 days of the month for example) and add a statement like in this example:

If FinancialStatementToDate length is 7, we concatenate '-01' or '-15' to the end. The customer should decide on and implement this.

We have the valid date formats below that are supported for enrichment.

yyyy-MM-dd
MM/dd/YYYY
MM.dd.YYYY
MM-dd-YYYY
YYYY/MM/dd
YYYY-MM-dd
YYYY.MM.dd
YYYYMMdd

If this is impossible, please change the Date data type to String for all the DnB Date attributes in the L3 configuration.