Codeunit 5187 "Job Module"

ContosoCoffeeDemoDataset · Microsoft.DemoData.Jobs · BC29-30 · source at ea08af5e · facts from BC29

Procedures

• RunConfigurationPage()
• GetDependencies(): List of [enum "Contoso Demo Data Module"]
• CreateSetupData()
• CreateMasterData()
• CreateTransactionalData()
• CreateHistoricalData()

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 5189 “Create Job Item Jnl Lines” (1 call: CreateTransactionalData → (object))
• Codeunit 5190 “Create Job” (1 call: CreateTransactionalData → (object))
• Codeunit 5191 “Create Job Resource” (1 call: CreateMasterData → (object))
• Codeunit 5192 “Create Job Item” (1 call: CreateMasterData → (object))
• Codeunit 5194 “Create Job Posting Group” (1 call: CreateSetupData → (object))
• Codeunit 5195 “Create Job No Series” (1 call: CreateSetupData → (object))
• Codeunit 5196 “Create Job Location” (1 call: CreateMasterData → (object))
• Codeunit 5197 “Create Job Journal Setup” (1 call: CreateSetupData → (object))
• Codeunit 5198 “Create Job Item Journal” (1 call: CreateSetupData → (object))
• Codeunit 5199 “Create Job GL Account” (1 call: CreateSetupData → (object))
• Codeunit 5210 “Create Job Setup” (1 call: CreateSetupData → (object))
• Page 4764 “Jobs Module Setup” (1 call: RunConfigurationPage → (object))

Implements

• Enum 5160 “Contoso Demo Data Module”

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