• [fix] Project BOM: manually assign parts
• [fix] Swagger UI

• Setting up workspace at start-up optimized so it runs faster
• [fix] Purchase orders: receive items with the same Manufacturer PN and Manufacturer but with different Supplier PN
• [fix] Project builds: when assembling items with reserved inventory, set default inventory on the ComboBox
• [fix] Go-to and scroll to table row
• [fix] Memory leak related with prices displayed on tables making the app slower

• [fix] Parts filters: Value filter missing
• [fix] Parts: set storage location when creating a new part
• [fix] Price columns with paywall tag on professional plans

• Parts: Label column can now be grouped
• Import parts: allow to import data of existing parts so data can be overwritten in bulk
• Import purchase orders: status (open, ordered or received) can now be defined when importing purchase orders
• [fix] Some rows missing when grouping some columns
• [fix] Aggregated data on some grouped columns

Grouping by Label​

• BOM copy
• Parts group edit: package, value, NRFND and non-stocking fields added
• Export table to PDF improved
• Merge purchase orders: only purchase orders in the Open state can be merged
• Merged purchase orders: group by Supplier PN and see aggregated data
• [fix] CSV and JSON table export: arrays and internal ids

Copying BOMs​

You can now copy a project revision's BOM from another project revisions's BOM. This is especially useful for models/variants: different projects that have a very similar BOM, ofen the difference being on the parts that are (not) to be populated (DNP).

Merged Purchase Orders: Aggregated Data​

A purchase order always keeps track of purchase lists that originated them. When merging two purchase orders, the resulting purchase order might contain duplicate parts, each one coming from a different purchase list. By grouping the table by Supplier PN you get to see not only the rows corresponding to each purchase list but also the aggregated value on top. If, for example, you want to export into a CSV file only the aggregated values, you simply collapse the grouped row.

To merge purchase orders, they have to have the same supplier and to be in the Open state.

• Import parts with inventory in multiple storage locations
• Add Inventory: allow to add inventory even if quantity = 0 (but the Storage location is set)
• Auto-assign quotes now works with selected items (instead of all items in the table)
• Auto-assign quotes and Unassign quotes now have its own button
• Small UI fixes and improvements
• [fix] Custom quotes not found

• [new feature] Inventory value report
• Parts new fields: Unit Cost, On-hand (in-house stock), Worth
• Import purchase orders from custom suppliers
• Storage tab performance improvements
• Man. Part Number, Int. Part Number and Supplier Part Number renamed to Manufacturer PN, Internal PN and Supplier PN
• Parts filters: Internal PN added
• Parts filters: Manufacturer PN added back to fuzzy-search (still has its own "exact match" search filter)
• [fix] Chance of intermittent read-only mode in team workspaces
• [fix] Part finder: filter parts
• [fix] Ensure workspace has a name upon its creation

Inventory Value Report​

You can now easily check how much is your inventory worth. This is accomplished through a new field in Parts: Unit Cost. This value can be manually set or imported along with new Parts. But the best thing is that it's also automatically updated whenever you use Purchasing, so whenever a Purchase Order is received, or imported, the unit cost for each part will be updated.

The inventory value report can be exported into CSV, PDF or HTML and is available on professional plans.

• Barcode labels now include the Internal Part Number
• Storage descriptions show on the Storage tree
• Custom barcodes can be generated through the API
• Part search filters: Man. Part Number doesn't use fuzzy search
• [fix] Import parts without storage assigned: not listed as unallocated
• [fix] Table columns re-ordering (drag and drop)
• [fix] Custom fields: respect fuzzy search option
• [fix] Extra re-render after workspace initialization
• [fix] API: swagger documentation

• BOM preferences: set fields part data should be matched to when importing a BOM
• BOM export: revision is set on PDF
• Barcodes include a line feed to avoid additional barcode scanner configuration
• [fix] Import purchase order: purchase orders are set as "received"
• [fix] Storage: tree node is updated after editing storage
• [fix] Unselect project build when current project revision changes
• [fix] Barcode reader buffer flush timeout increased
• [fix] Project revision finder dialog

Import BOM: Part Fields to Match​

When importing a BOM, parts would be automatically assigned to each BOM entry if a part on your workspace would match the Man. Part Number and Manufacturer or simply the Man. Part Number. From now on, you can set which fields should be matched. Custom fields can be leveraged to match parts to a custom ID for example or any other value you might find useful. Multiple matching fields can be set.

If more than a part is found for a given match, the part won't be automatically assigned.

• [fix] Printing issues (file not found), open printer preferences (windows-only)
• [fix] Error dialog at startup