Import & Export
To export or import workspaces, look for the corresponding buttons on the top right corner of the app.
Exporting a workspace results in a
.bomist_dump file that you then can import into another workspace if needed. Importing a workspace into another doesn't delete any data on the destination. Instead, it just incrementally adds up data.
All tables in the app can be exported into
HTML by right-clicking on it and selecting
Export.... When exporting tables, its current configuration is respected so you might want to adjust it to fit your needs. To quickly switch between table configurations you can create and make use of Views.
When exporting a table into PDF, because you are limited by the paper's size, you might need to adjust the table's current View and in particular the visible columns and their sizes so they fit in the page.
Importing data into tables is normally done through CSV files. Depending on the data you are importing, the app expects some fields to be passed which you can then map to the columns in your CSV file.
When loading a CSV with headers that match the fields the app expects, the headers get automatically mapped. For example, if the app expects a
Part Number to be passed and there's an header with that exact name in the CSV file, then it gets automatically mapped.
When importing data you'll be prompted with a merge confirmation dialog highlighting the new nodes, so you can review the changes resulting from importing data into existing one.
Another way you can use to import or export data is by using the API. You can export the whole workspace (into a
.bomist_dump file) through the API if needed or simply fetch and process the specific data you need.