3469064 - Error in Boomi Custom Integration Due to Date Format Mismatch in Position OData API

You are encountering an error in your custom Boomi integration, where you are using the Position OData API.

Below is the error:

Cleansing failed on data element: "SFOData.Position/createdDate (Function: CleanseDateTimeFail)". The thrown message was: [SFOData.Position/createdDate (Function: CleanseDateTimeFail)]: null

• SAP SuccessFactors HCM Suite
  • Boomi

The root cause of the error is a change in the date and time format of the "createdDate" and "lastModifiedDate" fields of the Position OData API. This results in a date format different from what the integration expects. 

Upon checking the logs, you notice that the error is generated due to the 2 fields: "createdDate" and "lastModifiedDate".

It appears that the date format for these 2 fields has been changed.

According to the profile, the date format for these 2 fields is: yyyy-MM-dd'T'HH:mm:ss.SSSZZ

However, upon checking, it can be seen that the actual format for these fields is: yyyy-MM-dd'T'HH:mm:ss.SSS'Z'

Due to this inconsistency, you are receiving the error.

According to the update from the Boomi team, they recently released an update in April that addressed the issue with the date and time format validation.

As a result of this change, the Boomi team suggests that you update all date fields to the appropriate format "yyyy-MM-dd'T'HH:mm:ss.SSS'Z'".

In other words, the old date format you are currently using is deemed inappropriate and should be rejected. This discrepancy represents a defect, as the inappropriate format was accepted in the previous release.

In the April release, Boomi resolved this issue, and only the appropriate format will now be accepted.

Boomi, integration, error, OData API, Position, date format, createdDate, lastModifiedDate, logs, SAP, update, cleanse shape, validation, date and time format, fix. , KBA , LOD-SF-INT-BOM , Standard SF to 3rd Party Boomi Content , Problem