Expand storage location export to include # of each item on hand.

[cielf]

Summary

Expand current storage location export to include # of each item on hand.

Why

Some of our banks have several storage locations. Although they can see what is in each storage location, it would be handy to have it all in one sheet.

Details

• Expand the current storage location export (which is not very useful) to also have the items-on-hand
• With one column per active item, whether or not there are any on-hand
• The columns must be in a stable order

See also Issue #3388

Additional Info

Original ask

Submitted By

Laurie Rovin (Laurie@periodproject.org)

Description

Can you create an export by storage location

Priority

Medium - It is seriously effecting our operations

Expected Behavior

Need to know total quantity on hand per location and per item

Actual Behavior

Get total quantity, but not sorted by location. Thank you for your help!

Notes

CLF 20230206 I think what is actually wanted here would be an expansion of the storage location to have the items-on-hand, akin to what we have for distribution, etc. 1 column for each active item that is in the system, even if they don't happen to have any on-hand in any storage location at the moment. Laurie's no longer with TPP, so we can't ask if that's what she meant

Criteria for completion

• functionality as described is available
• tests to support that functionality

[kev-kev]

@cielf Quick question on this- Right now, the Total Inventory column in the export is including inactive items in the value. Do we want to leave it like this if inactive items are now being hidden in the export? Should I update @storage_controller.size to not include inactive items? Something else?
Thank you!

[cielf]

@kev-kev An excellent question. In an ideal world it wouldn't be an issue, because they wouldn't make an item inactive if they had any.
Would it be easy to have a Total Active Inventory, and a Total Inventory (including Inactive)?

[github-actions]

This issue has been inactive for 246 hours (10.25 days) and will be automatically unassigned after 114 more hours (4.75 days).

[github-actions]

This issue has been inactive for 366 hours (15.25 days) and is past the limit of 360 hours (15.00 days) so is being unassigned.