You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When creating a property with a reference to a ConceptDescription, the ConceptDescription does not come up in the property. A label saying “ConceptDescription cannot be looked up within the AAS environment!“ is shown.
To get the correct behavior, I need to manually assign the ConceptDescription.
To Reproduce
Steps to reproduce the behavior:
Create a property.
In the “Editing of entities” for the property, click Concept Description: “Create empty” button.
A Concept Description and a corresponding semantic id reference on the property will be created.
Label in the property saying: “ConceptDescription cannot be looked up within the AAS environment!“.
In the “Editing of entities” for the property click Concept Description: “Use existing” button.
Navigate to the desired ConceptDescription and select it in the menu.
The property will show the ConceptDescription as expected.
Expected behavior
When a property has a semantic id to a ConceptDescription, it should not be needed to manually assign it.
This screencast shows the expected behavior.
Why is this a problem
It is too cumbersome to have to manually reselect Concept Descriptions for every property.
The text was updated successfully, but these errors were encountered:
When creating a Concept Description from the “Create empty” button on the property, the semantic id reference on the property becomes a “ModelReference”.
When selecting a Concept Description with the “Use existing”, the semantic id reference on the property becomes a “ExternalReference”.
By switching the semantic id from “ModelReference” to “ExternalReference”, the Concept Description is shown in the property as expected.
Describe the bug
When creating a property with a reference to a ConceptDescription, the ConceptDescription does not come up in the property. A label saying “ConceptDescription cannot be looked up within the AAS environment!“ is shown.
To get the correct behavior, I need to manually assign the ConceptDescription.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
When a property has a semantic id to a ConceptDescription, it should not be needed to manually assign it.
This screencast shows the expected behavior.
Why is this a problem
It is too cumbersome to have to manually reselect Concept Descriptions for every property.
The text was updated successfully, but these errors were encountered: