Hi @Daumantas and team, I serialize a textual v2 model into json, and store it in a v2 API compliant repository (OpenMBEE flexo) When I retrieve the model as json from that repository, due to the nature of those technologies, the json elements are not anymore in the order as when the model was se…

Hi @Robert_Karban , One approach could be to make 2+ passes when parsing This is already the case with JSON deserialization, there is a pre-pass that populates a map of (element_id, Element) for resolving local references, including owned elements. For example, this works and prints an empty diff…

Thank you. I think there’s a misunderstanding or I’m missing something. Yes, the parsing of the textual model works in any order of declaration. I’m talking about the json representation. In your example the json that is deserialized is the same that is serialized. In the case i describe, the …

Hi Robert, you should be able to embed files into your posts now

[image] Robert_Karban: In the case i describe, the order of the json elements to deserialize is random although the elements are the same as the result of the serialization. The order beyond the first element should not matter. Only the first mapping pass inserts elements in the order they ar…

Hi @Zygimantas files uploading works now but json extension is blocked. I will send them in an email to you!

Ok sent files to @Zygimantas , @Daumantas I didnt have your email..

flexo.json.txt (425.2 KB) raw.json.txt (388.1 KB) here are the two files raw is what syside serializes flexo is what flexo returns - out of order

Thanks, I can reproduce the issue with both flexo.json (after moving Namespace to the front), and raw.json. Issue seems to be that ReferenceSubsetting owned related element is deserialized as unonwed element which ends its deserialization early, leaving it as an orphan element which does not work wi…

Great! Yea the orphan is a blocking issue. Don’t worry too much about the root namespace. We already handle that. It’s easy.

Ownership deserialization fixed for future release (likely v0.8.2). Also added simple inference for root element, either a Namespace (not subtype) without owning relationships, or the last ancestor of the first element in the array following either owning namespaces, owning related elements, or own…

Json deserialization requires elements to be in order

Syside Bug Reports

Daumantas October 8, 2025, 2:57pm 17

v0.8.1 has been released

Topic		Replies	Views
Json serialization/deserialization is not symmetric Bug Reports resolved , automator , sysmlv2	19	191	October 6, 2025
Minimal JSON round-trip with external/library references produces unresolved-reference warnings and non-identical derived relationships after reconstruction Bug Reports automator	6	140	August 3, 2026
Json serialization/deserialization bugs Bug Reports resolved , automator	6	159	November 18, 2025
Serialize/deserialize of interface and flows fails Discussion automator	3	90	May 27, 2026
'Component' missing in deserialized model Bug Reports resolved , automator	4	87	October 8, 2025

Json deserialization requires elements to be in order

Related topics