[Bug]: AASX Server cannot interpret Serialization Modifier #329
Labels
bug
Something isn't working
Comments
hofermo
added a commit
to mnestix/mnestix-browser
that referenced
this issue
Jul 17, 2024
…Modifiers (#30) As the AASX Server does not support SerializationModifiers (eclipse-aaspe/server#329) I removed the call.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Contact Details
[email protected]
Describe the bug
When trying to access a Submodel using a SerializationModifier the server returns a 400 Bad Request HTTP Code.
To reproduce
Try to access the data of a submodel using the API using the following link template:
Screenshots
Expected Behaviour
The Metadata representation of the submodel or a behaviour similar to BaSyx, getting the complete submodel
Version
docker.io/adminshellio/aasx-server-blazor-for-demo:main
Operating System
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered: