The first nightly run of the new Mendix 11.15.0 job (added by mendixlabs#1293) fails: https://github.com/mendixlabs/mxcli/actions/runs/37265807529/job/111622280565. Every other version passes; only mdl/executor fails, with two tests. Both reproduce locally with mxbuild 11.15.0.
Cause: Mendix 11.15 replaced message-definition collections
Measured by mx convert (11.15.0) of an 11.14 project made with mdl-examples/doctype-tests/40-message-definition-examples.mdl:
- Collection → folder + documents. A
MessageDefinitions$MessageDefinitionCollection unit becomes a Projects$Folder with the same unit ID and the collection's name (MD_Order). Each entry becomes its own MessageDefinitions$MessageDefinition2 document inside it.
- Document shape. Each document has
Name, Documentation, Excluded, ExportLevel and ExposedEntity. The ExposedEntity tree is byte-identical to the old entry, apart from $IDs.
- Mapping link. An import or export mapping loses the
MessageDefinition key entirely. MessageDefinition: "MsgTest.MD_Order.OrderMessage" becomes MessageDefinition2: "MsgTest.OrderMessage", i.e. module plus message name.
- Blank-app mappings. In a blank 11.15 app (FeedbackModule), mappings have
MessageDefinition2: "" and no MessageDefinition key.
Symptoms
TestMappingFixtureRoundTrip. FeedbackModule.EXM_PostFeedback and IMM_PostResponse do not round-trip. The writer always adds "MessageDefinition": "", which the 11.15 document does not have. Per the overlay rule, Studio Pro may refuse a document with an unknown property, so this affects every mapping write on 11.15.TestMxCheck_DoctypeScripts/40-message-definition-examples.mdl. CE0270 "No root element could be found in the schema" at MsgTest.IMM_Order. The mapping's source is written to MessageDefinition, which 11.15 no longer reads.- Not covered by a test. On a converted (or Studio Pro 11.15) project,
show message definition collections finds nothing. describe import mapping MsgTest.IMM_Order prints no with message definition clause, so describe → exec would rebuild the mapping with no source.
The first nightly run of the new Mendix 11.15.0 job (added by mendixlabs#1293) fails: https://github.com/mendixlabs/mxcli/actions/runs/37265807529/job/111622280565. Every other version passes; only
mdl/executorfails, with two tests. Both reproduce locally with mxbuild 11.15.0.Cause: Mendix 11.15 replaced message-definition collections
Measured by
mx convert(11.15.0) of an 11.14 project made withmdl-examples/doctype-tests/40-message-definition-examples.mdl:MessageDefinitions$MessageDefinitionCollectionunit becomes aProjects$Folderwith the same unit ID and the collection's name (MD_Order). Each entry becomes its ownMessageDefinitions$MessageDefinition2document inside it.Name,Documentation,Excluded,ExportLevelandExposedEntity. TheExposedEntitytree is byte-identical to the old entry, apart from$IDs.MessageDefinitionkey entirely.MessageDefinition: "MsgTest.MD_Order.OrderMessage"becomesMessageDefinition2: "MsgTest.OrderMessage", i.e. module plus message name.MessageDefinition2: ""and noMessageDefinitionkey.Symptoms
TestMappingFixtureRoundTrip. FeedbackModule.EXM_PostFeedback and IMM_PostResponse do not round-trip. The writer always adds"MessageDefinition": "", which the 11.15 document does not have. Per the overlay rule, Studio Pro may refuse a document with an unknown property, so this affects every mapping write on 11.15.TestMxCheck_DoctypeScripts/40-message-definition-examples.mdl. CE0270 "No root element could be found in the schema" atMsgTest.IMM_Order. The mapping's source is written toMessageDefinition, which 11.15 no longer reads.show message definition collectionsfinds nothing.describe import mapping MsgTest.IMM_Orderprints nowith message definitionclause, so describe → exec would rebuild the mapping with no source.