eclipse-aaspe / package-explorer

AASX Package Explorer
Other
55 stars 20 forks source link

ConceptDescription cannot be looked up within the AAS environment! #11

Closed JS-Aibel closed 6 months ago

JS-Aibel commented 8 months ago

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:

  1. Create a property.
  2. In the “Editing of entities” for the property, click Concept Description: “Create empty” button.
  3. A Concept Description and a corresponding semantic id reference on the property will be created.
  4. Label in the property saying: “ConceptDescription cannot be looked up within the AAS environment!“.
  5. In the “Editing of entities” for the property click Concept Description: “Use existing” button.
  6. Navigate to the desired ConceptDescription and select it in the menu.
  7. 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.

JS-Aibel commented 8 months ago

I figured out what triggers it.

  1. When creating a Concept Description from the “Create empty” button on the property, the semantic id reference on the property becomes a “ModelReference”.
  2. 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.

juileetikekar commented 7 months ago

HI @JS-Aibel,

Thank you for raising the issue !!

The described behavior was succeessfully reproduced. We will keep you updated further.