Skip to main content
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    Call Slip requests write to call_slip table with -1 as patron_db_id value

    • Article Type: General
    • Product: Voyager
    • Product Version: 8.1.0


    Problem Symptoms:

    • Unable to delete patron record in Circulation
    • Receive error: "Unable to delete patron. Patron has outstanding UB requests" (even if institution does not use UB)
    • Call slip requests write to the call_slip table with -1 as the patron_db_id value, instead of 0


    This behavior is a result of Issue 18708 / VYG-4211.


    Issue VYG-4211 is resolved for Voyager 9.1.0 and higher.


    Category: Circulation

    • Article last edited: 12/17/2015
    • Was this article helpful?