Skip to content

List widget over a reverse association ending on a generalization types its rows as the parent entity (CE1613) #975

Description

@Chendodelangen

List widget over a reverse association ending on a generalization types its rows as the parent entity (CE1613)

Steps to reproduce

CREATE PERSISTENT ENTITY MyModule.Base ("Title": String(200));
CREATE PERSISTENT ENTITY MyModule.Child EXTENDS MyModule.Base ("Own": String(20));
CREATE PERSISTENT ENTITY MyModule.Note ("Content": String(200));
CREATE ASSOCIATION MyModule.Note_Base FROM MyModule.Note TO MyModule.Base TYPE Reference OWNER Default;

create or modify page MyModule.Probe (
  Title: 'probe', Layout: Atlas_Core.PopupLayout, Folder: 'Pages',
  Params: { $Child: MyModule.Child }
) {
  dataview dv (DataSource: $Child) {
    listview lv (DataSource: $currentObject/MyModule.Note_Base) {
      container c {
        dynamictext t (Content: '{1}', RenderMode: Paragraph, ContentParams: [{1} = Content])
      }
    }
  }
}

Expected

Rows typed as MyModule.Note (the child/FROM side of the association), so Content resolves — that is what the same construction yields in Studio Pro.

Actual

[error] [CE1613] "The selected attribute 'MyModule.Base.Content' no longer exists." at Text 't'

The rows are typed as the association's TO side (Base). The identical construction works correctly when the association's TO side is the exact context entity (e.g. Line_Child with a $Child context): only the ends-on-a-generalization case mis-types.

Workaround

Feed such lists with a microflow datasource that retrieves the children.

  • Diagnostic bundle: available, mxcli-diag-20260827-184627.tar.gz

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions