Bug Report: CO records with the same attachmentID cannot be added to the same Accession | Accession Search Dialog does not display more than 10 Recordsets

Get Help
1

Specify 7 Version: issue-609
Git SHA: e1e47642f98ffc3e7e54c6cba50f79c3d38f9b2e

I had the great fortune today of encountering 2 bugs in one go while trying to add a bunch of CO records to an accession earlier. Both very frustrating: the first essentially completely blocks us from using an entire table until it’s fixed.

Bug 1: Adding CO records that share an attachmentID to an Accession triggers an “out of date” crash preventing a save.

Description: Adding CO records to an Accession using the Interactions Search Dialog (QB, Record Set, or simple search) works for any number of CO records as long as no 2 CO records in the set share an attachmentID (CO->COAttachment->AttachmentID). I’ve confirmed that this error does not affect these COs in Loan Interactions (I think this is because the Loan Interaction Search Dialog uses CatNos to create a list of preps, which don’t have duplicated AttachmentIDs), but it probably affects any interaction that has a direct relationship to the CO table. This issue persists whether CO records are added via the Accession form, or added manually from the CO records themselves by Accession QCBX.

This may be a somewhat unique bug in that most collections do not have duplicate attachmentIDs for COs, but we do (this was done for our collection during the conversion, I requested a to-many relationship between attachment and CO because it saved 2500% in attachment server space over the alternative: uploading the same ledger image attachments 25 times, once per CO.)

To reproduce:

Specify 7 Crash Report - 2025-07-02T19_09_17.794Z.txt (815.9 KB)

Bug 2: Search Dialog “Record Sets” button does not display a complete set of Record Sets, only 10 apparently random ones

Description: When clicking “Record Sets” in the Accession Interaction Search Dialog window (and possibly in other Search Dialogs), the user is shown a list of 10 random Record Sets, notably not the entire set of record sets for that user. It is unclear how the list is assembled (it isn’t ascending by date, nor is it organized by recordset ID).

To Reproduce:

  • Open any Accession record as a user with more than 10 record sets saved
  • Open search dialog with magnifying glass on CO subform
  • Click “Record Sets” and see that not all record sets appear.

Screenshot 2025-07-02 at 2.05.44 PM
Screenshot 2025-07-02 at 2.05.44 PM690×624 77.2 KB

2

Hello @nfshoobs,

Thank you for bringing the bug to our attention. I wanted to inform you that we have formally documented and submitted a bug report.

The issue is that the “Record Sets” button only displays a limited subset (observed to be a maximum of 10) controlled directly by the query page selector in the Queries :queries_: dialog.

Number of queries selector in Queries dialog
Number of queries selector in Queries dialog1564×912 141 KB

If you change this page size to “Unlimited”, it will resolve this issue when selecting a record set for the search dialog.

You can review the complete bug report at the following GitHub link:

Regarding the first bug reported, we are still looking into it to ensure a thorough check. We will get back to you soon!

1 Like