Open foprs opened 8 months ago
Hi @foprs,
We could not reproduce the provided exception stack trace (Screenshot 1, highlighted lines) with the attached AASX File. Also the file name from the exception does not match with the provided one.
However, from high-level analysis it seems, that an empty "valueId" was modelled for a submodel element. This means, the valueId (of type reference) consists of a type but no keys.
Could you please check for any such occurrances in the modelled file? If yes, please add at least one key or delete the valueId itself. Also, if possible, could you please share the exact file for us to reproduce the exact issue?
I did some tests with reduced models. In the attachment there is "test_aas_a.aasx" and "test_aas_b.aasx". When loading "test_aas_b.aasx" an error occurs.
The difference between the both model lies in the last concept description "TimeSeries". The Data Specification record has not been created in "test_aas_a". In "test_aas_b" the record has been created but no reference is set.
In general I am questioning that there is made a difference between opening a aasx directly and loading via the server. I would think that the server is there to work collaboratively on asset shells. There will be drafts that should be loadable also when not all references (key, values) are set.
Question 1) What is checked when loading from the server in difference to loading the file directly into the AASPE? 2) Why is this differentiation made?
Describe the bug We have established a connection with a local AASX-Server (via AASX File Repository/Connect HTTP/REST....) When loading a aasx-file (double click on the file in the AASPE) from the server, AASPE throws an error. It is the same error independent from the file. When loading the same file directly into the AASPE no error is there (test file is attached below).
Expected behavior Loading the file without error into AASPE
Screenshots
test.zip
Desktop (please complete the following information):