Update Match Attributes Request Deletes Reference ID

It looks like a call to the  "Reference Identifier Request" endpoint to “Update” an existing SOR ID with new (or the same) sorAttributes data will delete the referenceid value from the corresponding row in the Matchgrid.

Example data

{{{"sorAttributes":{"names":[

{"type":"official","given":"John","family":"Doe"}

],"dateOfBirth":"2004-01-01"}}}}

Sending this request 3 times results in:

First time: Result is 201 (Created) with content like  {“referenceId”:”1015”}   

(“Inserted” in Log, database has a new row)

Second time: Result is 200 (OK), with empty content (Should this be empty?)                    

(“Updated” in Log, database row now has referenceid=null)

Third time: Result is 500 (Internal Server Error)                                                       

(I am guessing a DB constraint violation in MatchService->upsert)