Table 4765 "Service Module Setup"
ContosoCoffeeDemoDataset · Microsoft.DemoData.Service
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 6 connected objects and pages
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
- Service Location: TableRelation Table 14 “Location”
- Resource 1 No.: TableRelation Table 156 “Resource”
- Resource 2 No.: TableRelation Table 156 “Resource”
- Customer No.: TableRelation Table 18 “Customer”
- Item 1 No.: TableRelation Table 27 “Item”
- Service Item 1 No.: TableRelation Table 27 “Item”
- Service Item 2 No.: TableRelation Table 27 “Item”
Pages and codeunits on this table
- Page 4763 “Service Module Setup” (source 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.
- Codeunit 5116 “Create Common Customer/Vendor” (1 call:
InitServiceDemoDataSetup → DomesticCustomer1)
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.