Member Junction
    Preparing search index...
    interface EntityDocumentMetadataConfig {
        defaultTruncationLimit?: number;
        fields?: Record<string, EntityDocumentFieldConfig>;
        fieldStrategy?: "all" | "include" | "exclude" | "explicit";
        includeEntityIcon?: boolean;
        includeUpdatedAt?: boolean;
    }
    Index

    Properties

    defaultTruncationLimit?: number

    Global default truncation limit in characters for fields with MaxLength > 5000 or nvarchar(MAX). Default: 1000. Individual field overrides in fields take precedence.

    fields?: Record<string, EntityDocumentFieldConfig>

    Per-field overrides. The key is the entity field name. Only relevant when fieldStrategy is "include" or "exclude", or when you need to override truncation for specific fields under "all" mode.

    fieldStrategy?: "all" | "include" | "exclude" | "explicit"

    Strategy for selecting which fields go into vector metadata:

    • "all": include every non-PK, non-uniqueidentifier, non-binary, non-system field (current default behavior)
    • "include": only include fields listed in fields. Explicitly listed fields are honored even when the "all" heuristics would skip them (PKs, uniqueidentifiers, _mj* fields) — only binary column types remain unstorable.
    • "exclude": include all "all"-eligible fields EXCEPT those listed in fields
    • "explicit": the metadata object contains EXACTLY the fields listed in fields and nothing else — none of the system-injected keys (RecordID, Entity, TemplateID) are added, and includeEntityIcon / includeUpdatedAt flip to opt-in (default false). Use this to keep vector metadata minimal — e.g. only the fields you filter on. Field selection follows the same rules as "include".
    includeEntityIcon?: boolean

    Whether to include the entity icon in vector metadata. Default: true — except under fieldStrategy "explicit", where the default flips to false (explicit mode is opt-in for everything).

    includeUpdatedAt?: boolean

    Whether to include __mj_UpdatedAt in vector metadata for freshness display in search results. Default: true — except under fieldStrategy "explicit", where the default flips to false (explicit mode is opt-in for everything).