You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(odata-client): route Headers microflow to its own slot (#728, CE6808)
Follow-up to 045ee6f23. That fix mapped BOTH the "Configuration microflow"
and "Headers microflow" MDL keywords to the configuration slot, so on 11.10+ a
`HeadersMicroflow:` reference was written to ConfigurationEntityMicroflow —
Studio Pro then demanded a System.ConsumedODataConfiguration return type and
raised CE6808 against a microflow that (correctly) returns a list of
System.HttpHeader.
Mendix stores the two as distinct fields on 11.10+: ConfigurationEntity-
Microflow vs HeaderListMicroflow (before 11.10 they shared ConfigurationMicroflow
and were distinguished by return type). Track them as separate model fields:
- model gains a HeadersMicroflow field + ODataHeadersMicroflowBSONKey (11.10+ →
HeaderListMicroflow, else ConfigurationMicroflow).
- AST/visitor route the `HeadersMicroflow` keyword to the new field; the
executor, both writers, and both read paths carry it through; DESCRIBE emits
the matching keyword.
Verified end-to-end on the OData doctype example (11.12): HeadersConfigAPI now
stores HeaderListMicroflow, DESCRIBE round-trips `HeadersMicroflow:`, and CE6808
is gone. Combined with the capability-default revert, the doctype script's OData
errors drop from 36 to 9 (the remaining 9 are a separate published-service issue).
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
0 commit comments