You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a POSTed batch of Instances contains a record with no classifications, the batch is rejected with the message:
"errors": [ { "message": "must not be null", "type": "1", "code": "javax.validation.constraints.NotNull.message", "parameters": [ { "key": "instances[184].classifications[0].classificationNumber", "value": "null" }
No classification is increasingly common for certain types of records, notably electronic that will never be shelved. Suggest sending filler values -- hopefully just an empty array would do the trick
The text was updated successfully, but these errors were encountered:
I suspect this might be another example of #464, where the issue is that the failed record contains an object property which is missing one or more required properties.
classificationNumber is a required property of the classifications object.
At the time of writing the main branch contains changes which, in order to prevent this error when POST, clean out and report on missing required object properties. @banerjek could you try transforming one of your failing records using main and reposting?
If a POSTed batch of Instances contains a record with no classifications, the batch is rejected with the message:
"errors": [ { "message": "must not be null", "type": "1", "code": "javax.validation.constraints.NotNull.message", "parameters": [ { "key": "instances[184].classifications[0].classificationNumber", "value": "null" }
No classification is increasingly common for certain types of records, notably electronic that will never be shelved. Suggest sending filler values -- hopefully just an empty array would do the trick
The text was updated successfully, but these errors were encountered: