Skip to main content
ExLibris

Knowledge Assistant

BETA
 
  • Subscribe by RSS
  • Back
    Voyager

     

    Ex Libris Knowledge Center
    1. Search site
      Go back to previous article
      1. Sign in
        • Sign in
        • Forgot password
    1. Home
    2. Voyager
    3. Knowledge Articles
    4. Incorrect Due Date Shown in Discharge Window when override 'Item is charged' block

    Incorrect Due Date Shown in Discharge Window when override 'Item is charged' block

    1. Last updated
    2. Save as PDF
    3. Share
      1. Share
      2. Tweet
      3. Share
    1. Symptoms
    2. Defect Status
    3. Replication Steps
    4. Additional Information
    • Product: Voyager
    • Product Version: all
    • Relevant for Installation Type: Multi-Tenant Direct, Dedicated-Direct, Local, TotalCare

    Symptoms

    When you charge an already charged item to a different patron (prompting Voyager to give a block message stating 'Item is charged to another patron. Item will be discharged before charging out to this patron', which requires an override), the Due Date that displays in the discharge window is the new due date assigned by the new charge, not the due date from the original transaction that was just discharged.

    Defect Status

    Issue VYG-7965 is with Development.

    Replication Steps

    1. Find an item that is already charged out to a patron 
    2. Select a barcode from the above query, look it up in Circulation (Item>Search>Barcode), click on the Charged To icon and note the Due Date
    3. Find a patron (not the one the item is currently charged to), and charge that item barcode out to that patron
    4. Override the 'Item is charged to another patron. Item will be discharged before charging out to this patron' block, and note the new Due Date
    5. Click into the Discharge window – you'll see the new due date in the Due Date column, not the original due date noted in step 2

    Additional Information

    This is a display bug; if you check circ_trans_archive for the transaction, you'll see that the original due_date is preserved there.

     

     


    • Article last edited: 02-Mar-2022
    View article in the Exlibris Knowledge Center
    1. Back to top
      • Incoming records have location data, but import maps all MFHDs to same location
      • Incorrect duplication in Voyager ELINK_INDEX table
    • Was this article helpful?

    Recommended articles

    1. Article type
      Topic
      Content Type
      Knowledge Article
      Language
      English
      Product
      Voyager
    2. Tags
      This page has no tags.
    1. © Copyright 2025 Ex Libris Knowledge Center
    2. Powered by CXone Expert ®
    • Term of Use
    • Privacy Policy
    • Contact Us
    2025 Ex Libris. All rights reserved