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
Currently, it's not possible to retrieve the bodies and components belonging to a Named Selection. NamedSelection class only has 2 properties: id and name.
It would be useful to have a members property returning a list of the members belonging to the NS itself.
It would be even more useful if the object is returned rather than just the body/component id.
💡 Steps for implementing the feature
No response
🔗 Useful links and references
No response
The text was updated successfully, but these errors were encountered:
Right now, if the named selection is created through PyAnsys Geometry, this would be easy to implement. But you already need to pass the elements when creating the named selection, so it is not that "useful" I'd say - you already know which elements you used to create the named selection. Nonetheless, it could be implemented.
The problem comes if we are reading an existing design from the service. In that case, we need to implement the capability in the service to return the elements that make the named selection.
The backend team is going to open a user story to track this work.
📝 Description of the feature
Currently, it's not possible to retrieve the bodies and components belonging to a Named Selection.
NamedSelection
class only has 2 properties:id
andname
.It would be useful to have a
members
property returning a list of the members belonging to the NS itself.It would be even more useful if the object is returned rather than just the body/component id.
💡 Steps for implementing the feature
No response
🔗 Useful links and references
No response
The text was updated successfully, but these errors were encountered: