Member Junction
    Preparing search index...

    The stock lookup: browse by name for the empty query; for a typed one, an escaped LIKE on the column the user is searching, prefix matches first. The field's RelatedEntityFilter and the [FKExtraFilter] input apply to both, in SQL. { SearchMode: 'hybrid' } in [FKLookupOptions] ranks through the platform search API instead and hydrates the winners in search order.

    Subclass it rather than FKLookupStrategy when an app wants MJ's querying but its own grouping or decoration — fieldsFor and baseFilter are the hooks for that.

    Hierarchy (View Summary)

    Index

    Constructors

    Methods

    • The search API ranks across every searchable field of the related entity, so it answers only when the field opted into hybrid ranking AND the user is searching the name field — a column chosen on the scope pill needs a LIKE on that column. A field metadata marks as Dropdown is a small reference table the user is meant to read, and a composite key's search result is a compact key segment rather than a SQL literal to hydrate with an IN list; both take the LIKE path.

      Parameters

      Returns boolean