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

Table 4771 "Jobs Module Setup"

ContosoCoffeeDemoDataset · Microsoft.DemoData.Jobs

Across versions

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

Neighbourhood 8 connected objects and pages

Table 27 "Item" (relates to, 4 links)ItemTable 14 "Location" (relates to)LocationTable 156 "Resource" (relates to)ResourceTable 18 "Customer" (relates to)CustomerTable 208 "Job Posting Group" (relates to)Job Posting GroupPage 4764 "Jobs Module Setup" (pages and codeunits on it)Jobs Module SetupCodeunit 5116 "Create Common Customer/Vendor" (calls)Create Common Customer/VendorIntroduction to Contoso Coffee (Learn pages)Introduction to Contoso Coffee

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.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

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

Evidence 1 sources