Follow-up to #643, whose safety fix intentionally rejected named datasource values and retained the generic DataSource clause as a workaround.
The remaining capability gap is now independently reproduced and implemented on a fork: a pluggable-widget schema may declare several independent list datasource properties. A single generic DataSource value cannot represent them without fanning the same source out to every mapping, and DESCRIBE PAGE cannot round-trip them without retaining each schema key.
Expected behaviour
- Accept a real datasource expression under a declared datasource property key; continue rejecting scalar lookalikes.
- Resolve each datasource mapping by its key or alias before falling back to the generic single-source convenience form.
- Select datasource-dependent widget modes from the mappings for that mode, rather than from an unrelated widget-wide slot.
- Maintain entity context per mapping so dependent attributes bind to the correct entity.
- Emit named datasource keys from DESCRIBE PAGE whenever collapsing to one DataSource clause would lose source identity.
Scope
List datasources only. Mendix permits several list datasource properties but at most one object datasource property.
Validation
The fork implementation includes unit coverage for several simultaneous named sources, a public ComboBox regression fixture, a real Mendix 11.12.3 build with zero consistency errors, make build/test/lint/check-findings, and a round-trip assertion.
Proposed implementation: tjorim#2
This is deliberately a follow-up rather than a duplicate: #643 closed the silent-data-loss defect; this restores the deferred general named/multi-source capability safely.
Follow-up to #643, whose safety fix intentionally rejected named datasource values and retained the generic DataSource clause as a workaround.
The remaining capability gap is now independently reproduced and implemented on a fork: a pluggable-widget schema may declare several independent list datasource properties. A single generic DataSource value cannot represent them without fanning the same source out to every mapping, and DESCRIBE PAGE cannot round-trip them without retaining each schema key.
Expected behaviour
Scope
List datasources only. Mendix permits several list datasource properties but at most one object datasource property.
Validation
The fork implementation includes unit coverage for several simultaneous named sources, a public ComboBox regression fixture, a real Mendix 11.12.3 build with zero consistency errors, make build/test/lint/check-findings, and a round-trip assertion.
Proposed implementation: tjorim#2
This is deliberately a follow-up rather than a duplicate: #643 closed the silent-data-loss defect; this restores the deferred general named/multi-source capability safely.