BC Observatoryunofficial, made by waldo
tablePlatform, DevOps & Performanceofficial - Microsoftderived - from the source, no model text

Table 8906 "Email Scenario"

System Application · System.Email

Open in Claude8906.mdSource on GitHub

Across versions

  1. BC23-30present

Neighbourhood 1 connected objects and pages

Page 8895 "Email Scenarios FactBox" (pages and codeunits on it)Email Scenarios FactBox

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.

System Application · System.Email · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Access Internal

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 Scenario Enum “Email Scenario” — enum Enum 8890 “Email Scenario”; DataClassification SystemMetadata
2 Connector Enum “Email Connector” — enum Email Connector; DataClassification SystemMetadata
3 Account Id Guid — DataClassification SystemMetadata

Keys

  • PK: Scenario (clustered)

Pages and codeunits on this table

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: "Email Scenario"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources