Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
JS-Aibel opened this issue Jan 26, 2024 · 2 comments · Fixed by #183
Closed

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

JS-Aibel opened this issue Jan 26, 2024 · 2 comments · Fixed by #183
Assignees
Labels
bug Something isn't working InProgress This is actively being worked on

Comments

@JS-Aibel
Copy link

JS-Aibel commented Jan 26, 2024

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
Copy link
Author

JS-Aibel commented Jan 29, 2024

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
Copy link
Contributor

HI @JS-Aibel,

Thank you for raising the issue !!

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

@juileetikekar juileetikekar added the InProgress This is actively being worked on label Mar 6, 2024
@juileetikekar juileetikekar linked a pull request Mar 12, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working InProgress This is actively being worked on
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants