API set call does not delete current player when dobject is missing

Issue description

Given a store which uses dobjects, but topic T1 is missing its dobject. T1 is connected to T2 via an association type AT1. If a POST service peforms a set call on T setting a new topic T3 instead of T2, the fact sheet will display two statements instead of one. The existing statement was not deleted, but the new statement was added. It is necessary that the dobject is absent for this bug to surface, since everything work as expected when it is present.

Developer comments

The root problem here is that the dobject is missing from the file system. Currently Topincs tries to work around this, but actually this should just cause an exception.

Reporting date

2025-04-28

Reported by

Robert Cerny

Resolving date

2025-05-02

Resolved by

Robert Cerny

Resolved in version

Topincs 10.0.0

Part of

Missing dobjects should cause an exception(Change)

Work sessions

Start	2025-04-28T14:24:54
End	2025-04-28T17:23:01
Participant	Robert Cerny

Screencapture

webmBefore