rows.com

Track Legacy Part Numbers Without Losing Set History in Your Spreadsheet

Managing a Lego piece database in Excel can be streamlined while preserving essential information about element IDs.

3 min readMicrosoft Excel | Help & Support with your Formula, Macro, and VBA problems | A Reddit Community

The challenge of tracking legacy part numbers in a spreadsheet is one that many collectors and inventory managers know all too well. When a Lego piece's element ID changes but the design stays the same, the information becomes fragmented across rows or buried in cell notes. For the user who wants to keep pieces on a single row for quick totals, the temptation to rely on cell notes is understandable. But that approach creates a hidden layer of data that resists searching, filtering, and future analysis. It solves the immediate visual problem while quietly undermining the spreadsheet's long-term utility.

The better path is to treat the element ID as a distinct field with its own column, rather than forcing the old and new IDs into the same cell. This means dedicating one column for the current element ID and another for the legacy or alternate ID. The piece stays on its own row, the totals remain visible at a glance, and the historical record is preserved without sacrificing searchability. If a set's manual originally listed the old ID, that information lives in a dedicated column, ready to be filtered or referenced without decoding a note. This approach respects the user's desire for simplicity while acknowledging that spreadsheets are tools for both human eyes and machine queries.

The alternative, embedding notes inside cells, may feel cleaner at first, but it trades short-term neatness for long-term friction. Notes are invisible to most search functions, they complicate sorting, and they are easy to overlook when updating inventory. The user's instinct to keep the row intact is sound, but the solution lies in structuring the data vertically, not hiding it horizontally. By separating the element ID from its legacy counterpart, the spreadsheet becomes a more honest reflection of the part's history, one that supports both quick counting and deep dives into set-specific documentation.

For anyone facing this same dilemma, the takeaway is clear: resist the urge to compress information into a single cell. Use columns to represent the different versions of the ID, and let the row remain the anchor for the piece itself. This method keeps totals accurate, preserves the manual's original context, and ensures that future searches, whether by element ID or by set number, will return the full picture without guesswork. The spreadsheet should work with you, not against you, and that starts with giving every piece of data a home of its own.

From Microsoft Excel | Help & Support with your Formula, Macro, and VBA problems | A Reddit Community

Lego pieces each have a unique element id. Lego often replace an old element id with a new one, even though the piece and design id stay the same.

I’m trying to find the best and simplest way to sort these pieces on the same row, but still keep the information of which set has old/new element id to reflect the information originally released in the manual for a set.

Read the original at Microsoft Excel | Help & Support with your Formula, Macro, and VBA problems | A Reddit Community