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

Table 8907 "Email Account Scenario"

System Application · System.Email

Across versions

  1. BC23-30present

Neighbourhood 3 connected objects and pages

Page 8893 "Email Scenario Setup" (pages and codeunits on it)Email Scenario SetupPage 8894 "Email Scenarios for Account" (pages and codeunits on it)Email Scenarios for AccountSet up email in Business Central (Learn pages)Set up email in Business Cen…

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

Learn documents this table through its pages: Page 8893 “Email Scenario Setup” (1 Learn page).

Properties

Property Value
Access Internal
TableType Temporary

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 Integer — DataClassification SystemMetadata
2 Connector Enum “Email Connector” — enum Email Connector; DataClassification SystemMetadata
3 Account Id Guid — DataClassification SystemMetadata
4 Display Name Text[2048] Specifies the scenarios that are using the email account. via Page 8893 “Email Scenario Setup” DataClassification SystemMetadata
5 Default Boolean — DataClassification SystemMetadata
6 EntryType Option — DataClassification SystemMetadata
7 Position Integer — DataClassification SystemMetadata

Keys

  • PK: Scenario, Account Id, Connector (clustered)
  • Position: Position
  • Name: Display Name

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

Evidence 1 sources