Member Junction
    Preparing search index...

    Interface MJEntityRelationshipEntity_IEntityRelationshipUIConfiguration

    How this relationship appears on the parent entity's generated form.

    Nested under MJEntityRelationshipEntity_IEntityRelationshipConfiguration.UI so later UI concerns (group, default-expanded, badge) can sit beside inclusion without a migration.

    interface MJEntityRelationshipEntity_IEntityRelationshipUIConfiguration {
        FormRole?: "Primary" | "Detail";
        inclusion?: "None" | "More" | "Primary";
        join?: { fields: string[]; mode: "any" };
        sortKey?: number;
    }
    Index

    Properties

    FormRole? inclusion? join? sortKey?

    Properties

    FormRole?: "Primary" | "Detail"

    Alias of inclusion. 'Primary' maps to Primary, 'Detail' maps to More.

    inclusion?: "None" | "More" | "Primary"

    L1 inclusion on the parent form. Keyed conceptually by (parent, related entity), not by a single FK.

    • 'Primary' — first-class rail.
    • 'More' — candidate, parked in More.
    • 'None' — not a candidate. Not in More. Ranker never sees it.

    Omit = Auto (L2 ranker). See Forms Architecture §7d.

    join?: { fields: string[]; mode: "any" }

    Same-table OR of FKs for one parent-form section (Bill-To OR Ship-To Orders). Sibling ERs to the same related entity should be inclusion: 'None' so they do not sprout extra rail items.

    sortKey?: number

    Higher = earlier among first-class related rail items (after Details, after lead contributions such as Overview). Omit = 0.

    Settings

    Member Visibility

    On This Page

    Properties