Table 4771 "Jobs Module Setup"
ContosoCoffeeDemoDataset · Microsoft.DemoData.Jobs
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 8 connected objects and pages
ContosoCoffeeDemoDataset · Microsoft.DemoData.Jobs · BC29-30 · source at ea08af5e · facts from BC29
Learn documents this table through its pages: Page 4764 “Jobs Module Setup” (1 Learn page).
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 4764 “Jobs Module Setup” | TableRelation Table 18 “Customer” |
| 3 | Item Machine No. | Code[20] | Specifies the main number to use for the scenarios. via Page 4764 “Jobs Module Setup” | TableRelation Table 27 “Item” |
| 4 | Item Consumable No. | Code[20] | Specifies extra item number to use for the scenarios. via Page 4764 “Jobs Module Setup” | TableRelation Table 27 “Item” |
| 5 | Item Supply No. | Code[20] | Specifies s item number to use for the scenarios. via Page 4764 “Jobs Module Setup” | TableRelation Table 27 “Item” |
| 6 | Item Service No. | Code[20] | Specifies service item number to use for the scenarios. via Page 4764 “Jobs Module Setup” | TableRelation Table 27 “Item” |
| 7 | Resource Installer No. | Code[20] | Specifies the local resource number to use for the small unit scenarios. via Page 4764 “Jobs Module Setup” | TableRelation Table 156 “Resource” |
| 8 | Job Posting Group | Code[20] | Specifies the value of the job posting group code used on jobs. via Page 4764 “Jobs Module Setup” | TableRelation Table 208 “Job Posting Group” (Job Posting Group) |
| 9 | Job Location | Code[10] | Specifies the location code to use for the scenarios. via Page 4764 “Jobs Module Setup” | TableRelation Table 14 “Location” (Location where(“Use As In-Transit” = const(false))) |
Keys
- Key1: Primary Key
Procedures
InitRecord()(internal)InitJobModuleDemoDataSetup()
Relations
- Job Location: TableRelation Table 14 “Location”
- Resource Installer No.: TableRelation Table 156 “Resource”
- Customer No.: TableRelation Table 18 “Customer”
- Job Posting Group: TableRelation Table 208 “Job Posting Group”
- Item Consumable No.: TableRelation Table 27 “Item”
- Item Machine No.: TableRelation Table 27 “Item”
- Item Service No.: TableRelation Table 27 “Item”
- Item Supply No.: TableRelation Table 27 “Item”
Pages and codeunits on this table
- Page 4764 “Jobs 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:
InitJobModuleDemoDataSetup → 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: "Jobs Module Setup"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.