This issue can be identified by the borrowing system error: "Received unexpected undo shipped message for transaction from [lender symbol]".

The issue occurs if the current lender of the request (in OCLC) is the same that was stored on the request when it was shipped and checked in and, the value in OCLC is stored as lower case but the value in ILLiad is stored as uppercase. This causes the request to not match and prompt the undo shipped note.

Workaround: Some sites have reported that changing to another skin and back to original skin allowed Login As to work again.

The Client Error log may say the following: A thread exception has occurred.
System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.

Bug#3980

Repro Steps
1. Open a loan request in the staff client
2. Clone the request. The behavior is the same regardless of cloning to same user or different user and if the request is/is not opened after the process is completed.

The DLL is trimming any leading or trailing spaces from the password field within the web, whereas the client just runs the password as it's entered with the spaces. For example, if my password is "ABC" when logging in the client "ABC " fails, whereas it works in the web pages because the space is being removed.

Note: A space can exist within the password itself, e.g., "P@ss W0rd", as long as it's an accepted requirement in the Customization Manager. The spaces within the password will not be trimmed by the DLL.

Bug# 4490

This issues occurs when you change the skin then navigate to Open request>OCLC tab>Holdings tab.

Workaround: Restarting the client fixes the issue; however, you will need to restart the client each time you change the skin or else the error will occur again.

v9.0
Bug# 4481

Bug# 4474

Bug# 4393

An error message/feedback pop-up will appear when a staff user attempts to group transactions by a field (e.g., username) in dd stacks searching. The log will record this error as "Transaction number 0 not found".

v8.7 & 9.0
Bug# 4172

Bug#4007

Bug#3765

OCLC Requests that have a Worldshare ILL Status of Closed and disposition of Supplied cannot be opened in the OCLC Request form.

Bug#3787

The transaction status that displays on the lower left of the status bar on a request form is not visible when using some skins due to the color contrast with the default black text. See the attached example of the Office 2013 Dark Gray Skin. This status is visible in the Standard Display using Office 2016 Colorful and Office 2016 Dark.

v9.0
Bug#3991
Bug#4166

The error message "Nullable object must have a value" needs to be explained better on the prompt. The error appears when attempting to request an item when the OCLC request is in the Cancelled status.

Bug#3594

The "The TransactionNumber could not be determined from the OCLC request." error appears when a staff user clicks the show button on a borrowing request that is linked to an OCLC request in the Cancelled status.

Bug#3595

Workaround: request a new WSKey from OCLC Article Exchange. For more instructions see: https://support.atlas-sys.com/hc/en-us/articles/360011808274-Requesting-a-WSKey-from-OCLC-Article-Exchange

Bug#3788

v9.0
Bug#3789

Workaround: Place the Supplemental Information tab in its own section, then you and group and rename the other aspects of the template.

Bug#3758

Bug#3583

Outgoing Notifications grid columns reset their size whenever Outgoing Notifications is closed or the client is restarted. v9.0