• API: labels can now be created, updated and deleted
• Part Usage: the Rev for the part being used is displayed on the table as Rev (Part) whereas the Rev (Product) refers to the revision of the product/BOM the part is being used on
• Part Usage: context-menu Replace part... added, so the part being used on selected BOMs can be replaced by some other part
• Some performance improvements when removing data

• New setting Custom are preferred added under Settings - Quotes: when enabled, all custom suppliers are considered preferred so they don't have to be listed under the preferred suppliers setting
• "Remove if empty" setting under Settings - Parts - Inventory: inventory is automatically removed only if it's not associated with a Lot
• When importing CSV data the app is now smarter when attempting to auto-map fields (e.g. "Qty" is the same as "Quantity"). When importing POs from DigiKey or Mouser, the app will attempt to auto-map the expected fields (e.g. "DigiKey Part #" mapped to "Supplier PN")
• Importing POs: higher chances of finding parts data (in case they don't exist yet on the app)

• Initial setup time reduced at the expense of having some tables taking a bit longer to load the first time they are rendered.
• Unit cost on generic parts is now the weighted average of all its alternates by taking into account their stock on-hand. Before, the unit cost of a generic part was the simple average of the unit cost of its alternates.
• When importing custom quotes, part number and manufacturer are optional (useful when internal PN is used instead)
• Custom fields of type Option can now be displayed on the calendar (for the data types that support the calendar)
• More color options have been added to custom fields of type Option
• A pick-list can now be generated from a production build by right-clicking on the table and select Pick List.... This list is grouped by storage location, so you can more conveniently check all the parts and quantities that need to be picked for each storage location

• When splitting items with Designators on a production build, the designators can now be edited both on the source and destination so they are also correctly split
• Backport of previous versions in the main channel

• The Pricing & Availability table now uses the same engine as the Production Plans Availability table and an option to use alternate parts (or not) can be defined
• Backport of previous versions in the main channel

• Obsolete inventory is now considered on-hand (reflected on stock counters)
• [fix] Unable to adjust or move obsolete inventory

• New feature: Internal Part Number generator. Internal part numbers can now be automatically generated. The part number consists of a simple counter: every time a new part number is generated, the counter is incremented. You can also define multiple Series. Each Series keeps its own counter and add a prefix to the generated part number. If enabled, internal part numbers are generated whenever manually creating parts, bulk importing parts, or creating parts through the API.

• New feature: Obsolete Inventory. You can now change the status of available inventory, from available to obsolete (and vice-versa). The status can be changed by simply editing selected inventory (right-click and Edit inventory...). Obsolete inventory is inventory that's no longer usable but which you still want to keep track of. Obsolete inventory is ignored for all purposes other than tracking it and for calculating a part's Worth.

• Purchasing: a Rev column has been added which allows you to list revisioned inventory to be purchased (not necessarily for in-house parts)

• When importing a BOM, a Unit of Measure column might be mapped. If mapped, it is used to determine the unit of measure in case it's not included in the value mapped in Qty. This should be useful when the software you use to generate a BOM doesn't include the unit of measure along with the quantity.

• Defining depth when importing tree-structured data (e.g. Storage and Labels): a setting was added (Settings - General - Import) which allows to define a character that should be used to denote depth. This way you can have names that include a dash -, the character previously used (and still used by default) to denote depth in tree-structured data.

• Barcodes: a setting was added (Settings - Barcodes) which allows the description on a detailed barcode label to wrap either at a character or word.

• When adding parts and quantities into a purchase order from a purchase list, the unit of measure used in the purchase order will match the one from the selected quote. For example: if a purchase list indicates 150 screws to be purchased and you selected a quote with pricing for a "Box-of-100", you'd need to buy 2 "Box-of-100", being that quantity and unit of measure the ones to be listed in the purchase order.

• Calendar: events can be drag-and-dropped in order to change its date

• Production plans can now be imported through a CSV file
• When "going-to" something (e.g. a part), if filters are active and possibly preventing the item to show up on the table, a popup is displayed informing you of that including a button to quickly close filters so the item would become visible
• API: when creating parts, category field can be passed
• History: storage events are logged (storage created, moved or removed)
• When importing CSV files, the fields to map are now double-sorted: first by required ones and then alphabetically
• Some minor UI improvements

• Support for Future Electronics API added
• API: history endpoints added

• The app now detects identical parts whenever importing or manually creating parts. Identical parts are parts with the same Part Number but identical Manufacturer (e.g. "Wurth Electronics" vs "Würth Elektronik"). By default, identical parts are considered the same. When importing parts you'll be warned about identical parts, if any, and given an option to manually confirm if those parts are meant to be considered the same or not.

This should prevent having multiple parts listed on the app that actually represent the same one. Before, a different Manufacturer for the same Part Number would always be considered as a different part whenever importing or manually creating a part. Once created, parts are still considered unique / different based on both Part Number and Manufacturer as different manufacturers might use the same part number.

• A search input (Filter...) for basic search was added to the Issues table