While me and @jschumann were testing independently the parser, we noticed some features to fix or to add: - the following file has a repeated sub_sub_section along the row (the columns "Element" and "fraction"). If one has only two blocks of this sub_sub_section, the parsing is fine. If one adds a third block of columns, some errors are raised. - the filename of generated entries is currently the name of the m_def class + a sequential number, I think it should be picked from a quantity of the m_def class. - empty cells in excel file should not raise errors, just not fill the quantity - after loading and parsing one of this schemas and excel files, if I hit the reprocess button some entries change their process status in failure and opening them the error "Something went wrong in this part of the app (Javascript error)." is displayed. - These generated entries cannot be singularly deleted until I save them a second time and they are actually written into physical files To test the issue above, create an entry choosing "CatalystCollection" class and drop the excel file inside there: [entry_schema_basi.archive.yaml](/uploads/eee887b85facc5f272f06a30f7ff4944/entry_schema_basi.archive.yaml) [test_upload_w_3_elements.xlsx](/uploads/5ce89535e09f8934f4ba61e6b1cfc7ea/test_upload_w_3_elements.xlsx) @amgo is following us in testing