Page 4764 "Jobs Module Setup"
ContosoCoffeeDemoDataset · Microsoft.DemoData.Jobs
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 3 connected objects and pages
ContosoCoffeeDemoDataset · Microsoft.DemoData.Jobs · captioned “Contoso Coffee Project Demo Data” · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Contoso Coffee Project Demo Data |
| Extensible | false |
| SourceTable | Jobs Module Setup |
| PageType | Card |
| ApplicationArea | All |
Fields on this page
Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).
| Group | Control | Shows | ToolTip |
|---|---|---|---|
| Master Data | Customer No. | Customer No. | Specifies the customer number to use for the scenarios. |
| Item 1 No. | Item Machine No. | Specifies the main number to use for the scenarios. | |
| Item 2 No. | Item Consumable No. | Specifies extra item number to use for the scenarios. | |
| Item 3 No. | Item Service No. | Specifies service item number to use for the scenarios. | |
| Item 4 No. | Item Supply No. | Specifies s item number to use for the scenarios. | |
| Resource L1 No. | Resource Installer No. | Specifies the local resource number to use for the small unit scenarios. | |
| Posting Setup | Job Posting Group | Job Posting Group | Specifies the value of the job posting group code used on jobs. |
| Locations | Service Location | Job Location | Specifies the location code to use for the scenarios. |
Triggers
OnOpenPage
Relations
- source table Table 4771 “Jobs Module Setup”
Called by
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 5187 “Job Module” (1 call:
RunConfigurationPage → (object))
Documented on Microsoft Learn
Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).
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: "page", object_name: "Jobs Module Setup"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.