When I import from CSV why do I have to specify which columns I am importing? For many of the CSV I am importing for an assembly, there are 7 columns, but the "build assembly from CSV" option only lets you import 5 columns. These assemblies were exported from minimrp with the 7 columns but I cannot import them on a different device fully.
By: Support
Posted on: Aug 22 2017 at 03:31:02 PM
The need to specifiy columns is because MiniMRP can import a CSV file that was generated by other inventory programs. Because it can be 'ANY' other program there is no industry standard that specifies the layout of a CSV so you do need to tell MiniMRP which column contains the part number etc.
What 7 columns are you referring to? If you've exported a BOM from MiniMRP then that can contain over 20 columns and you might have edited it further with something like MSExcel so MiniMRP can't make any assumptions about the columns in the CSV.
I also don't know what you mean when you say "Import them on a different device". Do you mean that you want to export from one computer and import on another? Are these computers sharing the same database?
By: Guest
Posted on: Aug 22 2017 at 03:38:19 PM
MiniMRP generally assumes that the components will already exist in your inventory so there is usually no need for them to be IMPORTED again so those 5 columns are all that MiniMRP needs.
The "Build Assembly From CSV only needs the part number. It doesn't need description. It doesn't actually IMPORT anything. It simply uses the component part numbers to create a relationship between the parent assembly and the child components. Because the items already exist in the database all of the vendor and price details are joined automatically into the new BOM.
If you are exporting from one computer and importing on another unrelated computer (ie not sharing the same database) and the components do not exist in that computer's inventory yet then I would suggest first importing the components using the "Inventory>Import CSV" to first get the items into the inventory. Then using the "Build Partslist From CSV" you only need the part number to create the relationship between the parent assembly and the component.
Reply - add a comment to this topic.
You may enter letters, numbers and standard punctuation only. HTML and other scripts/tags will be rejected.
