BC Observatoryunofficial, made by waldo
tableAL Developmentofficial - Microsoftderived - from the source, no model text

Table 1308 "O365 Getting Started Page Data"

Base Application

Open in Claude1308.mdSource on GitHub

Across versions

  1. BC23present
  2. BC24declaration changed
  3. BC25-30unchanged

Neighbourhood 1 connected objects and pages

Codeunit 4030 "Client Type Management" (calls)Client Type Management

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 · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption O365 Getting Started Page Data
DataClassification CustomerContent

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 No. Integer —
2 Display Target Code[20] —
3 Wizard ID Integer —
4 Type Option — OptionCaption: ,Image,Text
11 Image Media —
12 Body Text BLOB —
13 Media Resources Ref Code[50] —

Keys

  • Key1: No., Display Target, Wizard ID, Type (clustered)

Procedures

  • GetPageBodyText(var O365GettingStartedPageData: Record "O365 Getting Started Page Data"; CurrentPageID: Integer; WizardID: Integer): Boolean
  • GetPageImage(var ImageO365GettingStartedPageData: Record "O365 Getting Started Page Data"; CurrentPageID: Integer; WizardID: Integer)

Plus 1 local procedures.

Calls

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: "table", object_name: "O365 Getting Started Page Data"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources