Closed andriusr closed 6 years ago
Regarding both questions: Yes, you can do that using a custom export. Import/Export are used for flat-file formats like Excel and CSV. They are not meant to transfer data across PartKeepr systems, which I assume that you are looking for. Can you clarify?
I do not see that these missing features limit most users - usually they import data from a flat file, foreign system or BOM.
If this is a critical stopper, you have two options: Either wait until these features are implemented or you can choose to sponsor those features (as in: Pay PartKeepr UG the implementation costs).
The purpose of these features is not to transfer parts accros partkeepr instances. If I would need this type of transfer, I would move complete database. It is to import parts from BOMs and EDAs. The list of user-important part parameters is infinite and it is not possible to make finite list, I guess. Meta parts are convenient for organizing stock and internal relationships, however, if one could not import them (and conditions are part of any metapart, there is no use if condition is not configured), again, entering everything by hand is a pain. Excel can be used not only for flat single datatable import. It depends on template. If template is provided one can easily copy/paste data for multi-datatable import. There should be facility to get templates before importing, though. Right now I decided to try some other alternatives. I would be happy to donate or support partkeepr, just due time pressure waiting is not an option.
Hmm it's a bit hard to fulfill a feature request without an example file.
What's possible is to implement a custom import using the PartKeepr API - but this heavily depends on the EDA and BOM formats. Can you provide examples for that?
No feedback given for an extended period of time, closing the issue.
Feel free to re-open if you have additional information.
System Information
How to reproduce
Importing exporting of the parts has some essential features missing: