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

Table 4765 "Service Module Setup"

ContosoCoffeeDemoDataset · Microsoft.DemoData.Service

Across versions

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

Neighbourhood 6 connected objects and pages

Table 27 "Item" (relates to, 3 links)ItemTable 156 "Resource" (relates to, 2 links)ResourceTable 14 "Location" (relates to)LocationTable 18 "Customer" (relates to)CustomerPage 4763 "Service Module Setup" (pages and codeunits on it)Service Module SetupCodeunit 5116 "Create Common Customer/Vendor" (calls)Create Common Customer/Vendor

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

Properties

Property Value
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 Primary Key Code[20] — DataClassification SystemMetadata
2 Customer No. Code[20] Specifies the customer number to use for the scenarios. via Page 4763 “Service Module Setup” TableRelation Table 18 “Customer”
3 Item 1 No. Code[20] Specifies the main number to use for the scenarios. via Page 4763 “Service Module Setup” TableRelation Table 27 “Item” (Item where(Type = const(Inventory)))
4 Service Item 1 No. Code[20] Specifies extra item number to use for the scenarios. via Page 4763 “Service Module Setup” TableRelation Table 27 “Item” (Item where(Type = const(Service)))
5 Service Item 2 No. Code[20] Specifies extra item number to use for the scenarios. via Page 4763 “Service Module Setup” TableRelation Table 27 “Item” (Item where(Type = const(Service)))
6 Resource 1 No. Code[20] Specifies the resource number to use for the small unit scenarios. via Page 4763 “Service Module Setup” TableRelation Table 156 “Resource”
7 Resource 2 No. Code[20] Specifies the resource number to use for the large unit scenarios. via Page 4763 “Service Module Setup” TableRelation Table 156 “Resource”
8 Service Location Code[10] Specifies the location code to use for the scenarios. via Page 4763 “Service Module Setup” TableRelation Table 14 “Location” (Location where(“Use As In-Transit” = const(false)))

Keys

  • Key1: Primary Key

Procedures

  • InitRecord() (internal)
  • InitServiceDemoDataSetup()

Relations

Pages and codeunits on this table

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

Evidence 1 sources