You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With electronic components, it is common for multiple sources to be available. In a relational database, it is easy to create another table that lists all the possible sources. It GitPLM, we currently list additional lines for each source, and the priority column is used to select the one that goes into the generated BOM.
When generating BOMs that get sent to manufacturing, it seems that having multiple columns for each source is the way things are done.
I don't like the idea of additional columns in the partmaster CSV files for 2nd/3rd sources, but perhaps this is the simplest.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
With electronic components, it is common for multiple sources to be available. In a relational database, it is easy to create another table that lists all the possible sources. It GitPLM, we currently list additional lines for each source, and the priority column is used to select the one that goes into the generated BOM.
When generating BOMs that get sent to manufacturing, it seems that having multiple columns for each source is the way things are done.
I don't like the idea of additional columns in the partmaster CSV files for 2nd/3rd sources, but perhaps this is the simplest.
Beta Was this translation helpful? Give feedback.
All reactions