tablePlatform, DevOps & Performanceofficial - Microsoftderived - from the source, no model text

Table 2681 "Data Search Setup (Table)"

DataSearch · Microsoft.Foundation.DataSearch

Across versions

  1. BC23-28not present
  2. BC29-30present

Neighbourhood 1 connected objects and pages

Codeunit 2687 "Data Search Setup Changes" (event subscribers, 2 links)Data Search Setup Changes

Open in the neighbourhood explorer

One hop out, from the extracted relations and call graph. Up to 40 shown; the sections below list them all.

DataSearch · Microsoft.Foundation.DataSearch · captioned “Search Setup (Table)” · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Search Setup (Table)

Fields

Explanation: the field’s ToolTip in the code; without one, the ToolTip of a page control bound to the field (marked via the page); without that, its Caption (marked caption) when that differs from the name.

No. Name Type Explanation Notes
1 Table No. Integer — TableRelation AllObjWithCaption.“Object ID” where(“Object Type” = const(Table)); DataClassification SystemMetadata
2 Table Subtype Integer — DataClassification SystemMetadata
3 Role Center ID Integer — DataClassification SystemMetadata
4 No. of Hits Integer — DataClassification CustomerContent
5 Table/Type ID Integer — AutoIncrement; DataClassification SystemMetadata
9 Table Caption Text[250] — FlowField: lookup(AllObjWithCaption.“Object Caption” where(“Object Type” = const(Table), “Object ID” = field(“Table No.”)))

Keys

  • Key1: Role Center ID, Table No., Table Subtype (clustered)
  • Key2: No. of Hits
  • Key3: Table/Type ID

Trigger event subscribers

Procedures

  • InsertRec(WithSubTypes: Boolean) (internal): Used for also inserting related records, e.g. for SalesHeader that has several subtypes
  • DeleteRec(WithSubTypes: Boolean) (internal): Used for also deleting related records, e.g. for SalesHeader that has several subtypes
  • GetProfileID(): Code[30] (internal)
  • GetRoleCenterID(): Integer

Triggers

OnInsert

Ask your agent

Procedure bodies are not stored here (D10). For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: bcatlas_resolve_node(object_type: "table", object_name: "Data Search Setup (Table)"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources