Settings and activity
106 results found
-
37 votes
An error occurred while saving the comment
Wes Osborn
supported this idea
·
-
40 votes
An error occurred while saving the comment
Wes Osborn
commented
You might also want to comment on this: https://portal.productboard.com/iii/6-innovative-product-status-board-new/c/932-additional-acquisitions-links-
If needed, you could also use this SQL in the item find tool:
SELECT
DISTINCT cir.ItemRecordID
FROM
Polaris.polaris.PurchaseOrders po WITH (NOLOCK)
JOIN
Polaris.polaris.POLines pol WITH (NOLOCK) ON po.PurchaseOrderID = pol.PurchaseOrderID
JOIN
Polaris.polaris.POLineItemSegments polis WITH (NOLOCK) ON pol.POLineItemID = polis.POLineItemID
JOIN
Polaris.polaris.LineItemSegmentToItemRecord lisir WITH (NOLOCK) ON polis.POLineItemSegmentID = lisir.POLineItemSegmentID
JOIN
Polaris.polaris.CircItemRecords cir WITH (NOLOCK) ON lisir.ItemRecordID = cir.ItemRecordID
WHERE
po.PONumber = 'YourPONumberHere' -
9 votes
Wes Osborn
supported this idea
·
-
42 votes
An error occurred while saving the comment
Wes Osborn
commented
This would be a very big CARROT to the sticks we're typically presenting to members for switching away from the desktop client. If they could quickly switch branches ONLY in Leap that would be a game changer. Even better if they didn't have to pick workstations.
Wes Osborn
supported this idea
·
-
76 votes
An error occurred while saving the comment
Wes Osborn
commented
Maybe one way of getting more delivery type information on the receipts would be to have a Printed Name in the branch record. Currently, there is a Display Name, if a Printed Name could be added that would be a helpful place to include the needed delivery/sorting information. That would mirror how InnReach works.
Wes Osborn
supported this idea
·
-
17 votes
Wes Osborn
shared this idea
·
-
13 votes
Wes Osborn
supported this idea
·
-
32 votes
Wes Osborn
supported this idea
·
-
29 votes
Wes Osborn
shared this idea
·
-
18 votes
Wes Osborn
supported this idea
·
-
32 votes
An error occurred while saving the comment
Wes Osborn
commented
It is wild to think that this date could be updated by anything other than a SQL Update. It shouldn't be exposed in any API or 3rd party integration.
Wes Osborn
supported this idea
·
-
33 votes
Wes Osborn
supported this idea
·
-
26 votes
An error occurred while saving the comment
Wes Osborn
commented
Yes, this would be a time saver for us as well. It would also be nice that if it wasn't going to work that it would provide a better error message. Right now I think it just says system or internal error, something really generic.
Wes Osborn
supported this idea
·
-
14 votes
An error occurred while saving the comment
Wes Osborn
commented
This would be SOOOO nice for all date pickers! Or use the OS/browser date picker, which would have this by default.
Wes Osborn
supported this idea
·
-
55 votes
Wes Osborn
supported this idea
·
-
12 votes
Wes Osborn
shared this idea
·
-
10 votes
An error occurred while saving the comment
Wes Osborn
commented
This also means that you can end up with overlapping side bars when you go into the settings area.
Wes Osborn
shared this idea
·
-
18 votes
An error occurred while saving the comment
Wes Osborn
commented
Our workaround is using the desktop client to populate this field or to make changes to staff accounts with this field (since you cannot save the account either).
Wes Osborn
shared this idea
·
-
10 votes
An error occurred while saving the comment
Wes Osborn
commented
I imagine this was set up as a generic message because it would otherwise "leak" information as to if this was a valid barcode making it easier to compromise an account. See this Open Worldwide Application Security Project guidelines for their recommendations: https://cheatsheetseries.owasp.org/cheatsheets/Authentication_Cheat_Sheet.html#authentication-and-error-messages
-
8 votes
An error occurred while saving the comment
Wes Osborn
commented
Even allowing the parameters to be defined like you would normally in SQL with the variables at the top of the statement would be helpful. Though I think these might get wrapped as CTEs which might not allow for that.
An error occurred while saving the comment
Wes Osborn
commented
Just curious are you normally inputting branch and/or library ids? Forever, I have wanted the ability for us to put in a variable like $LOGGED-IN-BRANCHID into Find Tool sql and it would swap it out for the user's branch. Same with LIBRARYID too.
(sorry, I'm now seeing in your screenshot that your example is a barcode search)
Though your option could be more veristable for other Find Tool searches. It might be cool if the staff person could *optionally* save the parameters they've used for each different search as well.
Wes Osborn
supported this idea
·
Deleting them would be tough from a system design perspective, but finding a way to hide them would be great!