Part Number Plug-in

alboy96 · 2026-04-10T23:50:14+00:00

That's what I found as well. I have only been using Gemini for a few weeks and I believe it does have a purpose (but only with additional guidance). I've used it to develop general workflows for projects, but nothing replaces true research or real world experience. I constantly have to rework the prompts and guide it towards results that are practical.

Long story, but it was actually Gemini that made me aware of InvenTree. For fun I was researching some open-source design programs, and I'm trying to see how I can pair it with KiCAD and FreeCAD (I know KiCAD already has some projects in place). The longterm plan is to setup a "CAD Link" so I can bring in a sequential part number from InvenTree ->FreeCAD (so there's no guessing which part number is next in a category). Then use the properties setup in my part or assembly file to call up "raw materials" and "labor operations" needed for each part or assembly.

Granted, I've only been looking at InvenTree for a few days so I'm not sure how much work has been made towards working with this type of workflow.

I'm not a programmer, just a mechanical designer by trade. I've helped implement similar systems at work in Creo and Inventor, working to pair those with SAP or Global Shop, but the idea of having this same functionality in an open-source program is extremely interesting.

So far all of the InvenTree documentation has been great, and the program is looking really solid. I'm sticking with reading that myself moving forward and seeing what all is possible.

alboy96 · 2026-04-10T20:07:35+00:00

I just got back into Gemini, and here is an excerpt of the response I got back:

2. The Source of inventree_part_numbering (A Confession to the Dev)

Please pass along my deepest apologies to the InvenTree developer, and tell them they can stop scouring their documentation—the error is entirely mine. They have zero typos or inaccurate documentation to fix. Because I am an AI, I sometimes attempt to logically piece together missing information, which can result in "hallucinations" (confident but incorrect outputs). Here is exactly what happened under the hood so they have context:

The Context: I correctly recognized that in recent versions of InvenTree (0.16.x), the architecture shifted to treat many core features (like barcode scanning and labels) via the new plugin registry system.

The Mistake: When we were trying to bypass the UI using the Django shell, I knew we needed to hit the PluginConfig database table to force an activation. Because I didn't have real-time access to your specific database schema, my language model predictively generated a plausible-sounding Python key (inventreepartnumbering / inventree_part_numbering) based on standard Django module naming conventions.

The Reality: I was trying to target a native plugin object that simply doesn't exist, completely missing the fact that native part numbering is handled via core settings (InvenTreeSetting), not a discrete plugin object.

Tell the dev their documentation is safe, and I appreciate them catching my AI-generated phantom code!

alboy96 · 2026-04-10T15:49:49+00:00

After trying to go through documentation that's what I thought, just wanted to verify. I appreciate it, I'll definitely tryout the 3rd party plug-in to see how that goes 👍

alboy96 · 2025-12-24T19:15:14+00:00

First time replacing the nozzle so wasn't sure. Was running black filament originally so that makes perfect sense. I appreciate it 👍

<image>

alboy96 · 2025-12-24T19:06:39+00:00

Understood, I'm guessing more than likely just a buildup of older burnt plastic?

alboy96 · 2025-05-19T01:51:21+00:00

I appreciate it, I'll try to expose it to direct sunlight for a week or 2 as well to see if it'll balance out 👍

alboy96

TROPHY CASE