+1 vote
Dear openLCA community,

i would like to export a process in excel to make some changes which would take forever in the openLCA front-end editor. When exporting a process in openLCA to Excel, a .xlsx file is generated. However, when i try to import such a file, regardless of whether I've made changes or not, openLCA seems busy but at the end is not importing anything. The log files do not show any error. More strange, however, is that when i manually convert the .xlsx to .xls with MS Excel the import of the .xls file works fine. Unfortunately, this is no solution since a lot of data gets lost when converting from .xlsx to .xls.

Does anybody experienced this problem as well and has a nice solution or go around?

If not, is there maybe another solution for not typing in data for processes manually?

Thanks a lot and best regards!
in openLCA by (580 points)
edited by

2 Answers

0 votes
by (580 points)
Best answer

Dear all,

i still dont know the actual cause of the problem but i figured out a go around:

  1. Open the database from which you want to export
  2. Export one or more processes as a JSON-LD
  3. Create a new and empty database
  4. Import the JSON-LD to the new database
  5. Export the processes as an Excel
  6. Now you can make changes in the Excel tables; if you like rename it within the Excel and change the UUID (changing one character is sufficient); save
  7. Import the Excel in any database

This works fine for me

0 votes
by (87.2k points)

Hi Walther,

"forever" is maybe not so nice but I agree that changing many processes via the user interface is not ideal. We use Python and SQL typically for that.

The import of Excel dataset works (so, "Why importing processes from Excel does not work?") is not correct:

Export process

Import process into empty database

Process in the previously empty database.

However, if you make a copy of the excel file and only change some numbers and text, e.g., then it will not be recognised as a new dataset, since the process is recognised by its UUID, and an overwrite or entering a copy of existing elements is only possible with JSON-LD files.

If you enter a different UUID in the excel however, then it will be recognised as a different process dataset, and can be imported (the yellow colour is not needed of course).

(and it is good to also change the name which I didn't do now).

by (87.2k points)
Yes that's correct, in 1.x, the excel import always never updates a process. JSON-LD import allows you to specify wether existing UUIDs should be overwritten. We could add this as an option to the excel import, an update yes/no option. Let us know.