pageService Managementofficial - Microsoftderived - from the source, no model text

Page 6087 "Filed Serv. Contract Cm. Sheet"

Base Application · Microsoft.Service.Contract

Across versions

  1. BC23-24not present
  2. BC25added
  3. BC26-30unchanged

Neighbourhood 3 connected objects and pages

Table 5974 "Filed Serv. Contract Cmt. Line" (relates to)Filed Serv. Contract Cmt. LineTable 5974 "Filed Serv. Contract Cmt. Line" (pages and codeunits on it, 2 links)Filed Serv. Contract Cmt. LineTable 5971 "Filed Contract Line" (calls)Filed Contract Line

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.

Base Application · Microsoft.Service.Contract · captioned “Filed Service Contract Comment Sheet” · BC25-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Filed Service Contract Comment Sheet
SourceTable Filed Serv. Contract Cmt. Line
PageType List

Fields on this page

Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).

Group Control Shows ToolTip
Comments Date Comment Date Specifies the date when the comment was created. from the table field
Comment Comment Specifies the comment itself. from the table field

Procedures

  • Caption(): Text

Triggers

OnAfterGetCurrRecord, OnOpenPage

Relations

Pages and codeunits on this table

Called by

From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.

Ask your agent

Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC29 call graph. 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: "page", object_name: "Filed Serv. Contract Cm. Sheet"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources