Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Part already in Inventree database, different MPN #113

Closed
martin323232 opened this issue Jan 5, 2023 · 3 comments · Fixed by #114
Closed

Part already in Inventree database, different MPN #113

martin323232 opened this issue Jan 5, 2023 · 3 comments · Fixed by #114

Comments

@martin323232
Copy link

For some components with different MPN and even some with different manufactuerer I get "part already in Inventree database"

GR67M20A and GR67M25A gets added to the same part in inventree.

image

@martin323232
Copy link
Author

Had to add a different name for the two grommets.

@eeintech
Copy link
Contributor

eeintech commented Jan 5, 2023

Hi there @martin323232

Here the problems is that those two parts can be differentiated as their name and description are the same on Digi-Key... and InvenTree does not accept a new part when those are the same.
The only way you can create a new part is to change the name, for instance for GR67M20A, you can append the MPN at the end of the name:
image

Before you do that, I just found a bug with that that I am going to fix in 0.6.5, give me a bit of time to release it, I'll let you know 😃

even some with different manufactuerer

If an InvenTree part already contains a manufacturer part with the same manufacturer and MPN then it will be skipped and won't be added to the database. In other cases:

  • If manufacturer name is different: it will always create a new manufacturer part but decision to create a new InvenTree part depends if its "name" and "revision" field are the same to other existing InvenTree part
  • If MPN is different: it will always create a new InvenTree part

@eeintech eeintech mentioned this issue Jan 5, 2023
@eeintech
Copy link
Contributor

eeintech commented Jan 5, 2023

0.6.5 is now on PyPI, let me know if the workaround works for you 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants