211.0.10
Issues Resolved ImportantImportant Info
ALL USERS MUST BE LOGGED OUT WHEN UPGRADING TO v21.1 FOR THE FIRST TIME. THIS IS BECAUSE WORKS ORDER FINISHED ITEM TRANSACTIONS WILL BE SWITCH TO BOM BUILD TRANSACTIONS, DUE TO HOW THE SAGE STOCK VALUATION REPORT HANDLES UNCONFIRMED TRANSACTIONS.
TRANSACTION HISTORY FOR UNCONFIRMED COSTS WHERE THE NOMINAL HAS NOT BEEN UPDATED WILL HAVE THE COST VALUE REDUCED TO 0. THIS IS TO FIX INCORRECT VALUES BEING SHOWN ON THE RETROSPECTIVE STOCK VALUATION REPORT.
Issues Resolved
Works Order Processing
- Fix to stop multiselect errors when changing the multiselect in one operation then opening a different operation
- Fix to stop adding the same machines to the operation multiselect multiple times
- Fix to stop operations being amended via the maintain operation screen as it should be handled in the subcontract management screen or subcontract tab on the works order
- 83397 Samuel Padbury 17/01/2022 20:50:05 WO – Fix to allow issue full batch to work correctly
- Fix to set the quantity in UOM when creating a works order
- Renamed the quantity in UOM column to be more clear
- Fix to stop throwing an error when closing when the build time calculation is still going
- Fix to stop the calculate the button on the sales order line have the dates show from the sub assemblies whilst the calculation is still going.
- Unit selling price not pulling through on quote when updating free text line (CASE17653)
- WONAme on BudgetActualSummaryView precision was incorrect (17648)
MRP
- Fix to get the date of the requirement correctly for stock on works order operations.
- ReasonDocumentNo extended to 255 to handle adding the job number
- Fix to show the project operation and description for suggested works orders in the reason number
- Fix to handle components and finished items being the same items on a BOM.
- Fix to stop an error occurring in MRP when a warehouse cannot be selected for a sub assembly line
- Fix to remove products from MRP
Date applied: January 25, 2022