-
Key: SYSMOAS-14
-
Status: open
-
Source: Dassault Systemes ( Mr. Tomas Vileiniskis)
-
Summary:
In the API PIM, under ElementNavigationService, there's a getElements service which is dedicated for dumping the entire model content at a given commit.
This is an overkill for a use case when only part of the model content (e.g. a package) is required to do analysis (or any other task) on.
While theoretical a workaround could be used via getRelationshipsByRelatedElement by retrieving all of the owned elements under specified owner, this would result in gazillion separate calls and would not be efficient under slower networks.
Proposal - introduce a new service getOwnedElements with an ability to collect all of the owned elements recursively under specified root or enrich getElements with optional arguments allowing to achieve the same.
-
Reported: SystemsModelingAPI 1.0b1 — Fri, 14 Jul 2023 10:43 GMT
-
Updated: Mon, 8 Apr 2024 18:24 GMT
-
Attachments:
- Element_Owned_Elements.html 589 kB (text/html)
- Element_Owned_Elements.ipynb 16 kB ()
SYSMOAS — No easy way to retrieve all elements under specified model scope
- Key: SYSMOAS-14
- OMG Task Force: Systems Modeling API and Services (SystemsModelingAPI) 1.0 FTF