Settings and activity
175 results found
-
2 votesKristen Tait supported this idea ·
An error occurred while saving the comment -
41 votesKristen Tait supported this idea ·
-
15 votesUNDER REVIEW · 0 comments · ILS - Polaris » Acquisitions, Serials & Item/Issue/Inventory Management · Admin →Kristen Tait shared this idea ·
-
66 votesUNDER REVIEW · 11 comments · ILS - Polaris » Acquisitions, Serials & Item/Issue/Inventory Management · Admin →Kristen Tait supported this idea ·
-
21 votesKristen Tait supported this idea ·
-
6 votesKristen Tait supported this idea ·
-
5 votesKristen Tait supported this idea ·
-
40 votesKristen Tait supported this idea ·
-
25 votesKristen Tait supported this idea ·
-
3 votesKristen Tait supported this idea ·
-
12 votesKristen Tait supported this idea ·
-
14 votesKristen Tait supported this idea ·
-
20 votesKristen Tait supported this idea ·
-
10 votesKristen Tait supported this idea ·
-
30 votesKristen Tait supported this idea ·
-
46 votesKristen Tait supported this idea ·
-
9 votesKristen Tait supported this idea ·
-
10 votesKristen Tait supported this idea ·
-
27 votesKristen Tait supported this idea ·
-
8 votesKristen Tait supported this idea ·
For now, would the Polaris to INN-Reach API logs (specifically API Message Diagnostics) help here? If you accessed them right away it shouldn't be too hard to figure out which transaction is the cancelled one. I can see our patrons' requests that are cancelled, but I don't have an example of an outside request that has been cancelled (I'll try to check and grab a screen shot when I do!).