ProtectedError at /api/specify/borrow/1365/ when deleting borrow

[grantfitzsimmons]

ProtectedError at /api/specify/borrow/1365/

("Cannot delete some instances of model 'Addressofrecord' because they are referenced through a protected foreign key: 'Borrow.addressofrecord'", <QuerySet [<Borrow: Borrow object (143)>, <Borrow: Borrow object (417)>, <Borrow: Borrow object (722)>, <Borrow: Borrow object (795)>, <Borrow: Borrow object (808)>, <Borrow: Borrow object (859)>, <Borrow: Borrow object (869)>, <Borrow: Borrow object (870)>, <Borrow: Borrow object (954)>, <Borrow: Borrow object (1012)>, <Borrow: Borrow object (1025)>, <Borrow: Borrow object (1092)>, <Borrow: Borrow object (1245)>, <Borrow: Borrow object (1315)>, <Borrow: Borrow object (1334)>, <Borrow: Borrow object (1420)>, <Borrow: Borrow object (1519)>, <Borrow: Borrow object (1585)>, <Borrow: Borrow object (1660)>, <Borrow: Borrow object (1685)>, '...(remaining elements truncated)...']>)

RBGE reports being unable to delete this record due to the above error.

https://herbrbge-edge.test.specifysystems.org/specify/view/borrow/1365/

Specify 7 Crash Report - 2022-11-29T21_41_04.770Z.txt

[maxpatiiuk]

Back-end bug.

FYI for new developers:

There is a /api/delete_blockers/ endpoint that tells front-end if a given resource can be deleted, or if some other resource depends on it.

That endpoint returns no blockers for this record:
https://herbrbge-edge.test.specifysystems.org/api/delete_blockers/borrow/1365/

Need to figure out why it doesn't report this dependency as a delete blocker

[maxpatiiuk]

Until then, a workaround is to manually delete the related records or make them reference a different borrow record.

[grantfitzsimmons]

Not solved by #2806

https://herbrbge6802-issue-1694.test.specifysystems.org/specify/view/borrow/1365/

[grantfitzsimmons]

@melton-jason was this solved by #2929?

[melton-jason]

This should not have been solved by #2929.
This should be fixed in #2806 (even if it is not fixed currently on that branch).

#2929 should have only improved this error message (and ones like it).