ODATA CLIENT - ConfigurationMicroflow option not supported

[acarum]

mxcli version || mxcli version v0.13.0
Mendix version | | 11.11.0
Scenario | I need to set the Configuration Microflow along the a Odata Consume Service
Expected output | the Configuration microflow should be checked and the Microflow should be filled
Experienced output |the Configuration remains the default Constants Only

[ako]

Fixed in 045ee6f23.

Root cause

Mendix renamed the storage field across versions. From the Rest$ConsumedODataService reflection metadata:

configurationMicroflow:       introduced 10.12.0, DELETED 11.10.0
configurationEntityMicroflow: introduced 11.10.0

mxcli wrote the pre-11.10 key ConfigurationMicroflow on every project. On your 11.11, Studio Pro no longer recognizes that field, so it silently ignored it and the "Configuration source" dropdown stayed on "Constants only" — even though describe odata client showed the microflow (mxcli read its own key back fine).

This wasn't a modelsdk regression — both engines produced identical BSON, and the key had actually been flip-flopped in the past (#573 switched to ConfigurationEntityMicroflow, a later commit reverted it). The reflection VersionInfos (Introduced/Deleted) is the authority, and it's unambiguous.

Fix

• New model.ODataConfigMicroflowBSONKey(major, minor) picks the key by project version: ConfigurationEntityMicroflow on 11.10+, ConfigurationMicroflow below.
• Wired into both writers (modelsdk + legacy).
• The read side coalesces every historical key, so a service authored by any Mendix version round-trips through DESCRIBE.

Verified end-to-end on an 11.12.0 project: the stored unit now uses ConfigurationEntityMicroflow and DESCRIBE round-trips. Added helper + write-key tests and a bug-test script.

One caveat

mxcli's model currently unifies the "Configuration microflow" and "Headers microflow" dropdown options into a single field, so this fix targets the configuration slot (ConfigurationEntityMicroflow). A true "Headers microflow" (HeaderListMicroflow on 11.10+) would need the model to distinguish the two — please open a separate issue if you need that variant.