How to obtain the correct diagramElementId for invokeSingleClickOnDiagramElementTool after dropOnDiagram?

[Muffelkopf]

I'm automating the SysON web workflow (General View): after dropping a model element (e.g. a package) onto a diagram with dropOnDiagram, I want to call invokeSingleClickOnDiagramElementTool to run the palette tool for adding existing nested elements to that package, without manual UI steps.

Problem:

• invokeSingleClickOnDiagramElementTool requires a diagramElementId that matches what the diagram UI uses (the element the tool should act on).
• When we copy diagramElementId from the browser’s Network tab (e.g. from getPalette or the invoke mutation), invokeSingleClickOnDiagramElementTool succeeds.
• When we use the only node id returned inside dropOnDiagram’s diagram { nodes { … } } payload, invoke often fails with an ErrorPayload and no useful message.

Is there a supported GraphQL read (or a documented field on an existing mutation) that returns the full diagram node tree (or at least the diagram element id for the diagram root / a given dropped package) for a given representationId / editing context?
Should dropOnDiagram be expected to return enough diagram.nodes (including ancestors or the invoke target) so clients can derive the correct diagramElementId for follow-up tool invocations? If not, what is the recommended way for API clients to obtain the same diagramElementId the web client uses?

[AxelRICHARD]

Hello,

Thank you for using SysON.

As you have probably saw, SysON is built upon Sirius Web. So your question/problem here is more a Sirius Web one.

First, I was surprised that the payload returning by the DropOnDiagram GraphQL mutation does not contain a Diagram with the node you dropped, but after investigating, I found that this Diagram is not the one after the drop but the one before the drop.

So here are some elements that may help you:

• In a SysON diagram, the graphical nodes displayed represents the Exposed elements of the ViewUsage on which the diagram has been created, not the "real" elements (e.g. Package, PartUsage) directly.
• You can use a GraphQL subscription on any graphical representation in SysON (any diagram, the Explorer view, the Details view).
• If you use Java, you have access to IDiagramIdProvider, which is able to to give you the id of a graphical node, based on its description.
• You may also drop the element (e.g. Package) and all its sub elements at once. Indeed, the input of the GraphQL mutation allows you to do that.

Furthermore, if you need professional support, you can also visit this page: https://doc.mbse-syson.org/syson/v2026.3.0/user-manual/support.html

Hope it will help you.

Best regards,