Replies: 3 comments 5 replies
-
I went through the exact same thing. I had an IPN and a description. The Name in the way it is presented could be anything, but like you said, it feels very much like a description in the demo. I don't think there is a best way to implement it. I imported IPNs into both fields since the Name field is required and left the description as is. |
Beta Was this translation helpful? Give feedback.
-
@motusRP Name and IPN have different restrictions and purposes. As @LastEdit pointed out, you can control the format part names are displayed in. |
Beta Was this translation helpful? Give feedback.
-
We also ise IPN in a fixed format like xxx.yyyyy.zzzz where each number is unique. The name in our case is the manufacturer part number. We have a 1:1 correlation between them. E.g. 1k resistor from KOA has adifferent IPN comared to a 1k resistor from Vishay. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm curious how people are using IPN and Name in Inventree. We are a small-er company that does consulting work and we're looking for a way to manage parts, inventory, builds, etc. and Inventree is looking like exactly what we need.
Looking through the Demo site, it seems that "Name" has been used either as generic words (Blue Table, Leg, Top, Chair, etc.) or as an abbreviated description (R_220k_0402_1%) that is expanded in the Description field into real english.
We do have an existing part numbering (IPN) system (it's a first cut, open for revision) that has a aa-bbbbb-ccc format where all digits are numbers.
Descriptions on existing parts are a comma-separated list of keywords. ie.
It looks like we would be better off putting our IPN into the Name field, and leaving IPN blank, because it's unlikely that we'd be able to come up with unique Names for everything we had that weren't just coded text in some way. At least an IPN system lets us create those names in an organized way and navigate them easily later. I can see how "Name" might work for a really small company with a few assemblies to manage, but if you expand to a company with 10's or 100's of assemblies and 100's or 1000's of parts, generating a unique name for each one will become impossible without an IPN system (or just using sequential numbers for parts... ugh).
I did do an import with Name and IPN matching, but that becomes awkward as Inventree seems to combine Name, IPN, and Description in lists, so you end up with things like this:
Where the number is duplicated unnecessarily. I tried leaving "Name" blank on import but it didn't like that.
Am I treading ground that others have treaded before? Or am I missing something fundamental?
Thanks in advance!
Beta Was this translation helpful? Give feedback.
All reactions