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(retrieve): keep owner-both reverse-list retrieve as database source (#726)
Refines the #726 fix (050147101). Removing the reverse-Reference → database
conversion entirely was too broad: an owner="both" Reference consumed as a list
genuinely cannot be an in-memory retrieve. A reverse AssociationRetrieveSource
over an owner-both Reference resolves to a SINGLE object in Mendix, so feeding
it to a loop/aggregate fails mx check with CE0100 (surfaced by
mdl-examples/doctype-tests/02-microflow-examples.mdl's M029_RetrieveByAssociation,
whose Order_Customer association is owner both).
Narrow the database fallback to exactly that case — Reference + owner both +
reverse (child side) + used as a list. Everything else stays an
AssociationRetrieveSource: owner-default reverse traversals (the #726 reporter's
scenario) remain memory retrieves and stay distinct from database retrieves,
and object-typed usages stay association retrieves.
Verified: owner-default `retrieve $x from $Parent/Assoc` → association source
(list), 0 errors; owner-both list usage → database source, 0 CE0100. The
02-microflow-examples doctype goes back to 0 errors and the #726 memory-vs-db
pair still round-trips distinctly.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
0 commit comments