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

Table 5169 "Contoso Module Dependency"

ContosoCoffeeDemoDataset · Microsoft.DemoTool

Across versions

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

Neighbourhood 1 connected objects and pages

Table 5161 "Contoso Demo Data Module" (relates to, 2 links)Contoso Demo Data Module

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.

ContosoCoffeeDemoDataset · Microsoft.DemoTool · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Access Internal
Extensible false
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 Name Enum “Contoso Demo Data Module” — TableRelation Table 5161 “Contoso Demo Data Module” (Contoso Demo Data Module); enum Enum 5160 “Contoso Demo Data Module”
2 DependsOn Enum “Contoso Demo Data Module” — TableRelation Table 5161 “Contoso Demo Data Module” (Contoso Demo Data Module); enum Enum 5160 “Contoso Demo Data Module”

Keys

  • Key1: Name, DependsOn (clustered)
  • Key2: Name

Relations

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

Evidence 1 sources