Codeunit 4785 "Manufacturing Media"

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

Properties

Procedures

• GetAirPotPicture(): Codeunit "Temp Blob"
• GetAirPotLargePicture(): Codeunit "Temp Blob"
• GetAirPotDuoPicture(): Codeunit "Temp Blob"
• GetAirPotLiteWhitePicture(): Codeunit "Temp Blob"
• GetAutoDripPicture(): Codeunit "Temp Blob"
• GetAutoDripLiteBlackPicture(): Codeunit "Temp Blob"
• GetAutoDripLiteRedPicture(): Codeunit "Temp Blob"
• GetAutoDripLiteWhitePicture(): Codeunit "Temp Blob"

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 5142 “Contoso Utilities” (8 calls: GetAirPotDuoPicture → GetFileStream, GetAirPotLargePicture → GetFileStream, GetAirPotLiteWhitePicture → GetFileStream, …)

Called by

• Codeunit 4770 “Create Mfg Item” (8 calls: CreateBOMAndRoutingItems → GetAirPotLiteWhitePicture, CreateBOMAndRoutingItems → GetAirPotPicture, CreateFlushingItems → GetAutoDripPicture, …)

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