1. UNIFYBroker Forum
  2. Ideas
0
Completed

Feedback on schema validation to be improved

Matthew Clark 13 years ago • updated by anonymous 9 years ago • 7

In testing for IDBCHRS-34, it has been found that some instances of the Chris21 connectors were correctly committing entities to the database, while some are not. Debugging shows that the connector is correctly pulling entities from the target system, meaning these are being lost before committing to the database.

UPDATE: This was found to be an issue with schema validation causing the commit to fail on the "IncludeItem" step. However, the feedback to the user at the moment is insufficient, and you can only find this by viewing the Identity Broker logs. The following should be added:

  • A warning message should be raised and displayed on the statistics page - for v4.0, this should point the user to the logs. A larger set of work would be to collect all the entities that failed validation and display this following an import.
  • Raise an alert with the alert engine
  • The following error message should be updated to include the schema key for readability and ease of use, rather than the Entity Id:

The entity 55d751c6-0409-4bc0-9e09-1302e715feef on the f3df77ea-0084-4480-84a7-02125264899d connector Chris21 DET failed validation 3 times for the following reasons: detbirdate is a required field and is not present.; detsex is a required field and is not present.; detterdate is a required field and is not present.


Schema Validation Message.png
Matthew Clark 13 years ago

Updating description based on additional findings, extending initial estimate

Matthew Clark 13 years ago

Attached screenshot of schema validation message in connector statistics

Matthew Clark 13 years ago

Error message improved:

The entity 102913 (098033e1-f6ff-474a-b671-58362047671d) in the connector Chris21 DET (f3df77ea-0084-4480-84a7-02125264899d) failed validation 2 times for the following reasons: detbirdate is a required field and is not present.; detsex is a required field and is not present.

Added a fix to the multi key value handling which would break if a key field was null. If the entity key is not present, the message will be as follows:

The entity 102913,<null> (098033e1-f6ff-474a-b671-58362047671d) in the connector Chris21 DET (f3df77ea-0084-4480-84a7-02125264899d) failed validation 2 times for the following reasons: detbirdate is a required field and is not present.; detsex is a required field and is not present.

Matthew Clark 13 years ago

Fixed issue where it would not differentiate between a full or a polling import for the message. This is now complete pending the addition of firing an alert via the alert engine.

Matthew Clark 13 years ago

Tony, could you look at adding the alert? Searching for IDB-302 should show where it needs to happen.

Tony Sheehy 13 years ago

Alerts have been included for all Errored/Warning change detection engine (connector-job)events, and can be seen on the home page. This is waiting on IDB-220 for views or messages depending on which way that goes (for correct display).

Matthew Clark 12 years ago

Issue closed.

Customer support service by UserEcho